From d65a28b14b55ef9a2fcd21b0774c63997ff4c235 Mon Sep 17 00:00:00 2001 From: John Weldon Date: Thu, 22 Feb 2024 17:57:32 -0700 Subject: [PATCH] Remove outdated guidance on preferring prometheus-nats-exporter (#187) --- README.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/README.md b/README.md index 4df5444..3d49d40 100644 --- a/README.md +++ b/README.md @@ -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