Skip to content

Commit

Permalink
Remove outdated guidance on preferring prometheus-nats-exporter (#187)
Browse files Browse the repository at this point in the history
  • Loading branch information
johnweldon authored Feb 23, 2024
1 parent 4a51ca0 commit d65a28b
Showing 1 changed file with 0 additions and 7 deletions.
7 changes: 0 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -238,13 +238,6 @@ nats_core_total_connection_count{nats_server_cluster="region1",nats_server_host=
nats_core_total_connection_count{nats_server_cluster="region2",nats_server_host="localhost",nats_server_id="NCBI75V5ASPJAEAR3VPS2YELXP7K6CUXXWAD5PB2SJ4BOIYQHU6JKV7A"} 0
```
We feel Prometheus is the right fit for this project, but it's worth noting
that this is not the recommended Prometheus archtecture, preferring ease of use
over installing and configuring a full monitoring infrastructure. For a more
robust monitoring architecture the
[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
should be placed and configured alongside every NATS server component.
## Docker Compose
An easy way to start the NATS Surveyor stack (Grafana, Prometheus, and NATS
Expand Down

0 comments on commit d65a28b

Please sign in to comment.