From dcfb7289419e8cf0b4983c2d2021b929f8c3f4cb Mon Sep 17 00:00:00 2001 From: Waldemar Quevedo Date: Mon, 24 Jun 2019 09:17:18 -0700 Subject: [PATCH] Updates to monitoring section --- nats_server/monitoring.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/nats_server/monitoring.md b/nats_server/monitoring.md index 84b8559..b1bcca1 100644 --- a/nats_server/monitoring.md +++ b/nats_server/monitoring.md @@ -4,7 +4,7 @@ To monitor the NATS messaging system, `nats-server` provides a lightweight HTTP The NATS monitoring endpoints support JSONP and CORS, making it easy to create single page monitoring web applications. -## Enabling monitoring +### Enabling monitoring from the command line To enable the monitoring server, start the NATS server with the monitoring flag `-m` and the monitoring port, or turn it on in the [configuration file](configuration.md#configuration-properties). @@ -23,6 +23,14 @@ $ nats-server -m 8222 To test, run `nats-server -m 8222`, then go to http://localhost:8222/ +### Enable monitoring from the configuration file + +You can also enable monitoring using the configuration file as follows: + +```yaml +http_port: 8222 +``` + ## Monitoring endpoints The following sections describe each supported monitoring endpoint: `varz`, `connz`, `routez`, and `subsz`.