UpdateProblemImprovement-阿里云帮助中心

Updates the details of a fault postmortem and improvement.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

gemp:UpdateProblemImprovement

update

*All Resource

*

None

Request syntax

POST /problem/improvement/update HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The request body.
problemId	integer	No	The fault ID.	12312
problemReason	string	No	The cause of the fault.	Fault cause A
recentActivity	string	No	The lookup table for recent activities (PROBLEM_RECENT_ACTIVITY).	2
injectionMode	string	No	The lookup table for injection methods (PROBLEM_INJECTION_MODE).	1
recoveryMode	string	No	The lookup table for recovery methods (PROBLEM_RECOVERY_MODE).	2
discoverSource	integer	No	The lookup table for discovery sources (PROBLEM_DISCOVER_SOURCE).	1
userReport	integer	No	The lookup table for user reports (PROBLEM_USER_REPORT).	10
monitorSourceName	string	No	The monitoring source.	Zabbix
relationChanges	string	No	The associated changes.	Associated changes
dutyUserId	integer	No	The ID of the fault owner.	1231
replayDutyUserId	integer	No	The ID of the postmortem owner.	1213
dutyDepartmentName	string	No	The department name.	Service group A
dutyDepartmentId	integer	No	The department ID (service group ID).	123123
remark	string	No	The remarks.	Remarks
clientToken	string	No	The idempotency check.	4361a0e1-6747-4834-96ce-0c4840fd3813
customProblemReason	string	No	The cause of the fault.	Improper monitoring alert threshold settings

Response elements

Element	Type	Description	Example
	object	The response structure.
requestId	string	The request ID.	4361a0e1-6747-4834-96ce-0c4840fd3812

Examples

Success response

JSON format

{
  "requestId": "4361a0e1-6747-4834-96ce-0c4840fd3812"
}

Error codes

HTTP status code	Error code	Error message	Description
404	ProblemNotExisted	The problem does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.