RestartEnvironmentFeature - Application Real-Time Monitoring Service

Restarts a feature.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
arms:RestartEnvironmentFeature	none	Environment acs:arms:{#regionId}:{#accountId}:environment/{#environmentId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
EnvironmentId	string	Yes	The ID of the environment.	env-xxx
RegionId	string	No	The region ID. Default value: cn-hangzhou.	cn-hangzhou
FeatureName	string	Yes	The feature name. Valid values: app-agent-pilot, metric-agent, ebpf-agent, and service-check.	metric-agent

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	2983BEF7-4A0D-47A2-94A2-8E9C5E63****
Code	integer	The status code. The status code 200 indicates that the request was successful.	200
Message	string	The error message returned if the request failed.	success.
Success	boolean	Indicates whether the request was successful. Valid values: true false	true
Data	string	The returned message.	success

Examples

Sample success responses

JSONformat

{
  "RequestId": "2983BEF7-4A0D-47A2-94A2-8E9C5E63****",
  "Code": 200,
  "Message": "success.",
  "Success": true,
  "Data": "success"
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation

No change history