Consul
Consul Watch
Command: consul watch
The watch command provides a mechanism to watch for changes in a particular
data view (list of nodes, service members, key value, etc) and to invoke
a process with the latest values of the view. If no process is specified,
the current values are dumped to STDOUT which can be a useful way to inspect
data in Consul.
There is more documentation on watches here.
Usage
Usage: consul watch [options] [child...]
The only required option is -type which specifies the particular
data view. Depending on the type, various options may be required
or optionally provided. There is more documentation on watch
specifications here.
Command Options
-key- Key to watch. Only forkeytype.-name- Event name to watch. Only foreventtype.-passingonly=[true|false]- Should only passing entries be returned. Defaults tofalseand only applies forservicetype.-prefix- Key prefix to watch. Only forkeyprefixtype.-service- Service to watch. Required forservicetype, optional forcheckstype.-shell- Optional, use a shell to run the command (can set a custom shell via the SHELL environment variable). The default value is true.-state- Check state to filter on. Optional forcheckstype.-tag- Service tag to filter on. Optional forservicetype.-type- Watch type. Required, one of "key,keyprefix,services,nodes,service,checks, orevent.-filter=<filter>- Expression to use for filtering the results. Optional forchecksnodes,services, andservicetype. See the/catalog/nodesAPI documentation for a description of what is filterable.
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_CACERTenvironment 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_CAPATHenvironment variable.-client-cert=<value>- Path to a client cert file to use for TLS whenverify_incomingis enabled. This can also be specified via theCONSUL_CLIENT_CERTenvironment variable.-client-key=<value>- Path to a client key file to use for TLS whenverify_incomingis enabled. This can also be specified via theCONSUL_CLIENT_KEYenvironment 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_ADDRenvironment 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/socketif 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_NAMEenvironment variable.-token=<value>- ACL token to use in the request. This can also be specified via theCONSUL_HTTP_TOKENenvironment 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-tokenargument orCONSUL_HTTP_TOKENenvironment variable. This can also be specified via theCONSUL_HTTP_TOKEN_FILEenvironment 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.