GetHotspotAnalysis - - Alibaba Cloud Dokümantasyon Merkezi

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

sysom:GetHotspotAnalysis

get

*All Resource

*

None

Request syntax

POST /api/v1/openapi/proxy/post/livetrace_hotspot_analysis HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	İstek gövdesi.
appType	string	Yes	Uygulama türü.	GR
beg_end	integer	Yes	Bitiş zamanı.	1725413948000
beg_start	integer	Yes	Başlangıç zamanı.	1725410348000
instance	string	Yes	Örnek kimliği.	i-2ze5ru5rjurix7f71sxv
pid	integer	No	İşlem PID'si.	1657494
table	string	No	Sorgulanacak tablonun adı.	prof_on

Response elements

Element	Type	Description	Example
	object	Yanıt şeması.
code	string	Hata kodu.	SysomOpenAPI.ServerError
data	string	Döndürülen veri.	"AliYunDun:1657494 process (1657494): Based on the provided hot spot call stack information, the hot spot is mainly concentrated on `__nanosleep_nocancel` and the related system call `SyS_nanosleep`, which indicates that the process is waiting for a specific time interval. This is usually caused by long sleep periods or high-frequency timed operations in the application, such as scheduled tasks and heartbeat detection.\n\nThe application code uses `nanosleep` to implement precise delay control when it needs to periodically perform certain checks or wait for external events. To optimize this situation, consider the following approaches:\n- Evaluate whether the frequency of scheduled tasks can be reduced.\n- Use condition variables instead of simple sleep waits to respond to faster event triggers.\n- If it is an I/O-intensive operation wait, consider optimizing the I/O path or improving I/O efficiency. Use the I/O diagnostic tool on the SysOM platform to further identify specific I/O bottlenecks."
message	string	Yanıt mesajı.	success
requestId	string	İstek kimliği.	2D693121-C925-5154-8DF6-C09A8B369822
success	boolean	Çağrının başarılı olup olmadığını gösterir.	True

Examples

Success response

JSON format

{
  "code": "SysomOpenAPI.ServerError",
  "data": "\"AliYunDun:1657494 process (1657494): Based on the provided hot spot call stack information, the hot spot is mainly concentrated on `__nanosleep_nocancel` and the related system call `SyS_nanosleep`, which indicates that the process is waiting for a specific time interval. This is usually caused by long sleep periods or high-frequency timed operations in the application, such as scheduled tasks and heartbeat detection.\\n\\nThe application code uses `nanosleep` to implement precise delay control when it needs to periodically perform certain checks or wait for external events. To optimize this situation, consider the following approaches:\\n- Evaluate whether the frequency of scheduled tasks can be reduced.\\n- Use condition variables instead of simple sleep waits to respond to faster event triggers.\\n- If it is an I/O-intensive operation wait, consider optimizing the I/O path or improving I/O efficiency. Use the IO diagnostic tool on the SysOM platform to further locate specific I/O bottlenecks.\"",
  "message": "\nsuccess",
  "requestId": "2D693121-C925-5154-8DF6-C09A8B369822\n",
  "success": true
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.