All Products
Search
Document Center

Microservices Engine:QueryMonitor

Last Updated:Nov 13, 2024

Queries the monitoring information.

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.

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.
OperationAccess levelResource typeCondition keyAssociated operation
mse:QueryMonitorget
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RequestParsstringNo

The extended request parameters in the JSON format.

{}
MonitorTypestringYes

The metric type. The following metric types are supported:

[Basic system metrics]

  • cpuUsage
  • memoryUsage
  • diskUsage
  • gcCount
  • gcTime

[Nacos registry]

  • serviceCount
  • writeCostTime
  • readCostTime
  • TPS regCenterTps
  • QPS regCenterQps

[Nacos configuration center]

  • publish
  • getConfig

[zookeeper]

  • TPS zk_TpsCount
  • QPS zk_QpsCount
  • zookeeper_AvgRequestLatency
regCenterQps
StartTimelongYes

The timestamp when the monitoring starts.

1666678376
EndTimelongYes

The timestamp when the monitoring ends.

1666678376
SteplongYes

The interval between data points. Unit: seconds.

7
InstanceIdstringYes

The ID of the instance.

mse-cn-****
AcceptLanguagestringNo

The language of the response. Valid values:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The data structure.

Messagestring

The message returned.

The request was successfully processed.
RequestIdstring

The ID of the request.

ADDD8AB7-8D1C-4697-A83E-410D2607****
Dataarray<object>

The details of the data.

6
dataobject

The details of the data.

podNamestring

The name of the pod.

mse-xxxxxx-xxxxxx-reg-center-0-0
clusterNamePrefixstring

The prefix of the name.

mse-xxxx-xxxxxx
valuesarray<object>

The details of the data.

valuesobject

The content of the data.

ErrorCodestring

The error code returned if the request failed.

mse-100-000
Successboolean

Indicates whether the request was successful. Valid values:

  • true: The request was successful.
  • false: The request failed.
true

Examples

Sample success responses

JSONformat

{
  "Message": "The request was successfully processed.\n",
  "RequestId": "ADDD8AB7-8D1C-4697-A83E-410D2607****",
  "Data": [
    {
      "podName": "mse-xxxxxx-xxxxxx-reg-center-0-0",
      "clusterNamePrefix": "mse-xxxx-xxxxxx",
      "values": [
        {
          "test": "test",
          "test2": 1
        }
      ]
    }
  ],
  "ErrorCode": "mse-100-000",
  "Success": true
}

Error codes

HTTP status codeError codeError messageDescription
400IllegalRequestInvalid request:%sInvalid request: %s
400InvalidParameterParameter error:%sRequest parameter error: %s
403NoPermissionYou are not authorized to perform this operation:%sYou do not have the permission to use this interface:%s
404NotFoundNot found:%sThe resource does not exist:%s
500InternalErrorConsole error. Try again later:%sConsole error. Try again later: %s

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

Change history

Change timeSummary of changesOperation
2023-04-25API Description UpdateView Change Details