1
0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00

Updates to monitoring section

This commit is contained in:
Waldemar Quevedo 2019-06-24 09:17:18 -07:00 committed by GitHub
parent aa12832f16
commit dcfb728941
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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. 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). 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 <a href="http://localhost:8222/" target="_blank">http://localhost:8222/</a> To test, run `nats-server -m 8222`, then go to <a href="http://localhost:8222/" target="_blank">http://localhost:8222/</a>
### Enable monitoring from the configuration file
You can also enable monitoring using the configuration file as follows:
```yaml
http_port: 8222
```
## Monitoring endpoints ## Monitoring endpoints
The following sections describe each supported monitoring endpoint: `varz`, `connz`, `routez`, and `subsz`. The following sections describe each supported monitoring endpoint: `varz`, `connz`, `routez`, and `subsz`.