All Products
Search
Document Center

Microservices Engine:ListNamingTrack

Last Updated:Aug 12, 2024

Obtains the trajectory data of a Nacos registry.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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:ListNamingTrackget
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RequestParsstringNo

The extended request parameters in the JSON format.

{}
InstanceIdstringYes

The ID of the instance.

mse_prepaid_public_cn-tl32d*****
ServiceNamestringNo

The name of the service.

fpx-xms-baseinfo
GroupstringNo

The group.

group
NamespaceIdstringNo

The ID of the namespace.

cd4d3703-e2a6-46b5-85c6-4447e4f****
IpstringNo

The IP address of the client.

172.16.183.232
StartTslongYes

The start timestamp. Unit: seconds.

1660238450
EndTslongYes

The end timestamp. Unit: seconds.

1665299698
PageSizelongYes

The number of entries to return on each page.

10
PageNumlongYes

The number of the page to return.

1
ReversebooleanNo

Specifies whether to sort the query results in chronological order or reverse chronological order. Default value: false.

  • true: sorts the query results in reverse chronological order.
  • false: sorts the query results in chronological order.
false
AcceptLanguagestringNo

The language of the response. Valid values:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The data structure.

HttpCodestring

The HTTP status code returned.

200
Tracesarray<object>

The data information.

object

The details of the data.

PushTimestring

The push time.

2022-12-16 11:48:07
NodeNamestring

The name of the node.

mse-197*****-167083******-reg-center-0-0
ClientIpstring

The IP address of the client.

120.40.32.235
ServerNamestring

The name of the service.

fpx-xms-baseinfo
Groupstring

The group.

prod
InstanceSizestring

The number of instances.

1
PushTimeAllstring

The total push time.

628ms
PushTimeNetworkstring

The push time for the network.

37ms
SlaTimestring

The duration that is specified in the service-level agreement (SLA).

628ms
PageSizelong

The number of entries returned per page.

10
PageNumberlong

The number of the returned page.

1
TotalCountlong

The total number of returned entries.

7
RequestIdstring

The ID of the request.

9916CBED-B2D5-5685-9129-4592FE1*****
Messagestring

The message returned.

The request was successfully processed.
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

{
  "HttpCode": "200",
  "Traces": [
    {
      "PushTime": "2022-12-16 11:48:07",
      "NodeName": "mse-197*****-167083******-reg-center-0-0",
      "ClientIp": "120.40.32.235",
      "ServerName": "fpx-xms-baseinfo",
      "Group": "prod",
      "InstanceSize": "1",
      "PushTimeAll": "628ms",
      "PushTimeNetwork": "37ms",
      "SlaTime": "628ms"
    }
  ],
  "PageSize": 10,
  "PageNumber": 1,
  "TotalCount": 7,
  "RequestId": "9916CBED-B2D5-5685-9129-4592FE1*****",
  "Message": "The request was successfully processed.\n",
  "ErrorCode": "mse-100-000",
  "Success": true
}

Error codes

HTTP status codeError codeError messageDescription
202TrackRegionNotSupport-
400duplicatedClusterAliasNameduplicated cluster alias nameThe instance name is duplicate. User another name.
400illegalRequestillegal request:%sInvalid request: %s
403NoPermissionYou are not authorized to perform this operation:%sYou do not have the permission to use this interface:%s
404clusterNotFoundcluster not foundThe cluster is not found.
500systemErrorsystem errorAn error occurred on the system. Try again later.

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