Consul Catalog List Nodes
Command: consul catalog nodes
Corresponding HTTP API Endpoint: [GET] /v1/catalog/nodes
The catalog nodes
command prints all known nodes and metadata about them.
It can also query for nodes that match a particular metadata or provide a
particular service.
The table below shows this command's required ACLs. Configuration of blocking queries and agent caching are not supported from commands, but may be from the corresponding HTTP endpoint.
ACL Required |
---|
node:read |
Examples
List all nodes:
Print detailed node information such as tagged addresses and node metadata:
List nodes which provide the service name "web":
Sort the resulting node list by estimated round trip time to worker-05:
Usage
Usage: consul catalog nodes [options]
Command Options
-detailed
- Output detailed information about the nodes including their addresses and metadata.-near=<string>
- Node name to sort the node list in ascending order based on estimated round-trip time from that node. Passing"_agent"
will use this agent's node for sorting.-node-meta=<key=value>
- Metadata to filter nodes with the given key=value pairs. This flag may be specified multiple times to filter on multiple sources of metadata.-service=<id or name>
- Service id or name to filter nodes. Only nodes which are providing the given service will be returned.-filter=<filter>
- Expression to use for filtering the results. Can be passed via stdin by using-
for the value or from a file by passing@<file path>
. See the/catalog/nodes
API documentation for a description of what is filterable.
Enterprise Options
-partition=<string>
- Specifies the partition to query. If not provided, the partition will be inferred from the request's ACL token, or will default to thedefault
partition. Partitions are a Consul Enterprise feature added in v1.11.0.
API Options
-ca-file=<value>
- Path to a CA file to use for TLS when communicating with Consul. This can also be specified via theCONSUL_CACERT
environment variable.-ca-path=<value>
- Path to a directory of CA certificates to use for TLS when communicating with Consul. This can also be specified via theCONSUL_CAPATH
environment variable.-client-cert=<value>
- Path to a client cert file to use for TLS whenverify_incoming
is enabled. This can also be specified via theCONSUL_CLIENT_CERT
environment variable.-client-key=<value>
- Path to a client key file to use for TLS whenverify_incoming
is enabled. This can also be specified via theCONSUL_CLIENT_KEY
environment variable.-http-addr=<addr>
- Address of the Consul agent with the port. This can be an IP address or DNS address, but it must include the port. This can also be specified via theCONSUL_HTTP_ADDR
environment variable. In Consul 0.8 and later, the default value is http://127.0.0.1:8500, and https can optionally be used instead. The scheme can also be set to HTTPS by setting the environment variableCONSUL_HTTP_SSL=true
. This may be a unix domain socket usingunix:///path/to/socket
if the agent is configured to listen that way.-tls-server-name=<value>
- The server name to use as the SNI host when connecting via TLS. This can also be specified via theCONSUL_TLS_SERVER_NAME
environment variable.-token=<value>
- ACL token to use in the request. This can also be specified via theCONSUL_HTTP_TOKEN
environment variable. If unspecified, the query will default to the token of the Consul agent at the HTTP address.-token-file=<value>
- File containing the ACL token to use in the request instead of one specified via the-token
argument orCONSUL_HTTP_TOKEN
environment variable. This can also be specified via theCONSUL_HTTP_TOKEN_FILE
environment variable.
-datacenter=<name>
- Name of the datacenter to query. If unspecified, the query will default to the datacenter of the Consul agent at the HTTP address.-stale
- Permit any Consul server (non-leader) to respond to this request. This allows for lower latency and higher throughput, but can result in stale data. This option has no effect on non-read operations. The default value is false.