Use GetDoctorReportComponentSummary to obtain a component analysis report from EMR Doctor - E-MapReduce

Operation description

get specify component's report analysis by EMR Doctor

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

emr:GetDoctorReportComponentSummary

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	Region ID.	cn-hangzhou
ClusterId	string	Yes	Cluster ID.	c-b933c5aac8fe****
DateTime	string	Yes	Report date.	2023-01-01
ComponentType	string	Yes	Select component filter type. Values: compute hive hdfs yarn oss hbase Valid values: compute : compute hive : hive hdfs : hdfs yarn : yarn oss : oss hbase : hbase	compute

Response elements

Element	Type	Description	Example
	object	The response parameters.
Data	object	The content of the report.
Score	integer	Score.	88
Summary	string	The summary of the report.	[Compute Check] Compute health score is 88, health status is good, keep it up Most tasks in the cluster are in a healthy state Cluster memory utilization is: 47.8%, which is low
Suggestion	string	Optimization suggestions.	Compute health score is 88, the cluster is in a healthy state, keep it up Compute task scan Scanned 1518 compute tasks in the cluster, including 209 tasks in an unhealthy state, 596 tasks in a sub-healthy state, and 713 tasks in a healthy state. Details: 1518 Tez tasks with a weighted average score of 88, memory usage accounts for 100.0% of the cluster, CPU usage accounts for 100.0% of the cluster, including 209 unhealthy tasks and 596 sub-healthy tasks; Click "View Details" in the task detail list below to view specific issues and solutions. The "Low-score Task Memory Time (GB*Sec) Top 20" table is sorted by memory time usage. Since large tasks may have a greater impact on the overall cluster, prioritize them. Low memory utilization The overall cluster memory utilization is 47.8%, which is low. Computing resources are wasted. Prioritize optimizing TOP tasks with high memory time usage but low memory utilization. Among them, the average memory utilization of Tez jobs is 47.8%
RequestId	string	Request ID.	DD6B1B2A-5837-5237-ABE4-FF0C8944****

Examples

Success response

JSON format

{
  "Data": {
    "Score": 88,
    "Summary": " [Compute Check] Compute health score is 88, health status is good, keep it up\nMost tasks in the cluster are in a healthy state\nCluster memory utilization is: 47.8%, which is low",
    "Suggestion": "Compute health score is 88, the cluster is in a healthy state, keep it up \nCompute task scan\nScanned 1518 compute tasks in the cluster, including 209 tasks in an unhealthy state, 596 tasks in a sub-healthy state, and 713 tasks in a healthy state. \nDetails:\n       1518 Tez tasks with a weighted average score of 88, memory usage accounts for 100.0% of the cluster, CPU usage accounts for 100.0% of the cluster, including 209 unhealthy tasks and 596 sub-healthy tasks;\nClick View Details in the task detail list below to view specific issues and solutions. The Low-score Task Memory Time (GB*Sec) Top 20 table is sorted by memory time usage. Since large tasks may have a greater impact on the overall cluster, prioritize them.\nLow memory utilization\nThe overall cluster memory utilization is 47.8%, which is low. Computing resources are wasted. Prioritize optimizing TOP tasks with high memory time usage but low memory utilization.\nAmong them, the average memory utilization of Tez jobs is 47.8% "
  },
  "RequestId": "DD6B1B2A-5837-5237-ABE4-FF0C8944****"
}

Error codes

HTTP status code	Error code	Error message
400	ConflictParameters	Parameters that must not be used together. %s
400	IncompleteSignature	The request signature is invalid.
400	InvalidAction	The action %s requested is invalid.
400	InvalidParameter	The specified parameter %s is not valid.
400	InvalidParameterValue	The input parameter %s is invalid or out of range.
400	MissingAction	The action %s requested is missing.
400	MissingParameter	The input parameter %s that is mandatory for processing this request is not supplied.
400	NotAuthorized	You do not have permission to perform this action. %s
400	ThrottlingException	The request was denied due to request throttling. %s
500	InternalError	The request processing has failed due to some unknown error, exception or failure.
404	ResourceNotFound	The resource not found by %s.
503	ServiceFailure	The request has failed due to a temporary failure of %s service.
503	ServiceUnavailable	The request has failed due to a temporary failure of the server.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.