2014-02-08 00:41:03 +00:00
---
layout: "docs"
page_title: "Commands: Monitor"
sidebar_current: "docs-commands-monitor"
2014-10-19 23:40:10 +00:00
description: |-
The `monitor` command is used to connect and follow the logs of a running Consul agent. Monitor will show the recent logs and then continue to follow the logs, not exiting until interrupted or until the remote agent quits.
2014-02-08 00:41:03 +00:00
---
2014-02-19 01:32:13 +00:00
# Consul Monitor
2014-02-08 00:41:03 +00:00
2014-02-19 01:32:13 +00:00
Command: `consul monitor`
2014-02-08 00:41:03 +00:00
2014-10-19 23:40:10 +00:00
The `monitor` command is used to connect and follow the logs of a running
2014-02-19 01:32:13 +00:00
Consul agent. Monitor will show the recent logs and then continue to follow
2014-02-08 00:41:03 +00:00
the logs, not exiting until interrupted or until the remote agent quits.
The power of the monitor command is that it allows you to log the agent
at a relatively high log level (such as "warn"), but still access debug
logs and watch the debug logs if necessary.
## Usage
2014-02-19 01:32:13 +00:00
Usage: `consul monitor [options]`
2014-02-08 00:41:03 +00:00
The command-line flags are all optional. The list of available flags are:
* `-log-level` - The log level of the messages to show. By default this
is "info". This log level can be more verbose than what the agent is
configured to run at. Available log levels are "trace", "debug", "info",
"warn", and "err".
* `-rpc-addr` - Address to the RPC server of the agent you want to contact
2014-12-15 18:16:43 +00:00
to send this command. If this isn't specified, the command checks the
CONSUL_RPC_ADDR env variable. If this isn't set, the default RPC
address will be set to "127.0.0.1:8400".
