All Products
Search
Document Center

Microservices Engine:ListListenersByConfig

Last Updated:Nov 20, 2024

Queries listeners based on configuration information.

Operation description

Note The operation is not provided in Nacos SDKs. For information about Nacos SDKs, see the official documentation.

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:ListListenersByConfigget
*Cluster
acs:mse:{#regionId}:{#accountId}:instance/{#InstanceId}
*EngineNamespace
acs:mse:{#regionId}:{#accountId}:instance/{#InstanceId}/{#NamespaceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RequestParsstringNo

The extended request parameters in the JSON format.

{\\"appGroup\\":\\"emas-zfive_prehost\\",\\"appName\\":\\"emas-zfive\\",\\"appStage\\":\\"PRE_PUBLISH\\",\\"appUnit\\":\\"\\",\\"bucId\\":\\"225902\\",\\"bucName\\":\\"Wireless\\",\\"provider\\":\\"aliyun\\"}
InstanceIdstringYes

The ID of the instance.

mse-cn-m7r1yurp00e
DataIdstringYes

The ID of the data.

zeekr-clueboss.yml
GroupstringYes

The name of the group.

prod
NamespaceIdstringNo

The ID of the namespace.

aaeb4d28-c9eb-4fa2-85f5-d03ce7ee8df1
AcceptLanguagestringNo

The language of the response. Valid values:

  • zh: Chinese
  • en: English
zh

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

HttpCodestring

The HTTP status code returned.

202
TotalCountinteger

The total number of entries returned.

7
Listenersarray<object>

The information about listeners.

Listenerobject

The data structure.

Ipstring

The IP address.

1.1.1.1
Md5string

The verification string.

23sdfdf
Statusstring

The status.

beta
Labelsobject

The label of the listener.

string

The key-value pairs of the label.

Versionstring

The current version of the listener. Valid values: gray and normal.

gray
RequestIdstring

The ID of the request.

75E1442F-11EC-567A-9CF0-5A36F7904F39
Messagestring

The message returned.

success
PageSizeinteger

The number of entries returned per page.

10
PageNumberinteger

The page number of the returned page.

2
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": "202",
  "TotalCount": 7,
  "Listeners": [
    {
      "Ip": "1.1.1.1",
      "Md5": "23sdfdf",
      "Status": "beta",
      "Labels": {
        "key": ""
      },
      "Version": "gray"
    }
  ],
  "RequestId": "75E1442F-11EC-567A-9CF0-5A36F7904F39",
  "Message": "success",
  "PageSize": 10,
  "PageNumber": 2,
  "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
2024-11-06The request parameters of the API has changed. The response structure of the API has changedView Change Details
2022-03-16The response structure of the API has changedView Change Details