SaaSHub helps you find the best software and product alternatives Learn more →
Top 23 Go Monitoring Projects
-
To monitor and analyze rate limiting metrics, we're using a combination of Redis and Prometheus. We're storing rate limiting metrics in Redis and then using Prometheus to scrape the metrics and display them in a dashboard. Here's an example of how we're storing rate limiting metrics in Redis:
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
Project mention: War Story: Debugging a Kafka 4.0 Consumer Lag Spike During a Product Launch Using Cilium 1.17 and Datadog 2026 | dev.to | 2026-04-28
This adds less than 2% overhead to your node’s CPU usage but exposes 14 Kafka-specific eBPF metrics that are critical for debugging lag. We’ve found that 72% of Kafka 4.0 lag incidents we’ve responded to in 2026 stem from node-level network policy issues that only eBPF can detect. If you’re using a different CNI, you can still use Cilium’s standalone eBPF probe https://github.com/cilium/cilium/tree/v1.17.2/contrib/kafka-probe to get these metrics without replacing your entire CNI. Always validate that kafka.heartbeat_drops_total is 0 in staging before every launch.
-
Project mention: I Tested 7 Self-Hosted Monitoring Tools on a $3 VPS in 2026 (Here's the One I Kept) | dev.to | 2026-05-15
# On the hub server mkdir beszel && cd beszel curl -L https://github.com/henrygd/beszel/releases/latest/download/beszel_Linux_x86_64.tar.gz \ | tar -xz ./beszel serve # On every agent server curl -L https://github.com/henrygd/beszel/releases/latest/download/beszel-agent_Linux_x86_64.tar.gz \ | tar -xz KEY="$(cat ~/.ssh/id_ed25519.pub)" ./beszel-agent # Add the agent in the hub web UI, paste the public key, done
-
bettercap
The Swiss Army knife for 802.11, BLE, HID, CAN-bus, IPv4 and IPv6 networks reconnaissance and MITM attacks.
-
Project mention: Kubelet Metrics: How cAdvisor and CRI Collect Kubernetes Stats | dev.to | 2026-05-28
raw handler
-
No. Portainer is web-only. You can open a container console through the Portainer web UI, but Portainer itself has no terminal interface. If you want a TUI, use Lazydocker or ctop.
-
Telegraf
Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.
Project mention: The Performance Battle the hardening of Vault and OWASP: What Matters | dev.to | 2026-05-07A common mistake we see is teams rejecting Vault hardening because they assume it will add 400ms+ p99 latency, a myth perpetuated by outdated blog posts from 2020. Our benchmarks of Vault 1.15 show that OWASP-compliant TLS 1.3 and rate limiting add only 12ms p99 latency, not 400ms. Before deciding against hardening, run the first code example (vault_owasp_benchmark.py) against your own Vault deployment to get real numbers for your workload. Use tools like https://github.com/influxdata/telegraf to collect latency metrics from production, and https://github.com/grafana/grafana to visualize percentiles over time. For read-heavy workloads (10k+ requests per second), the latency overhead is even lower (under 8ms p99) because TLS 1.3 has lower handshake overhead than TLS 1.2. We worked with a SaaS company that rejected hardening for 6 months due to latency fears, only to find after benchmarking that the overhead was 9ms p99, well within their 100ms SLA. They implemented hardening in 2 weeks, cut breach risk by 89%, and saw no customer impact. Always benchmark with your own traffic patterns, not generic numbers from the internet. Use the Go benchmark tool or Python script provided to test with your secret sizes, request patterns, and auth methods. If you see unexpected latency spikes, check for misconfigured cipher suites or rate limits that are too strict, not the hardening itself.
-
Project mention: VictoriaMetrics VS arc - a user suggested alternative | libhunt.com/r/VictoriaMetrics | 2026-04-26
-
sampler
Tool for shell commands execution, visualization and alerting. Configured with a simple YAML file.
-
thanos
Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
Thank you thanos-io: https://github.com/thanos-io/thanos/issues/8381#issuecomment...
-
-
-
I use self-hosted gatus to monitor my certs and other services' status.
It can send alerts to multiple alerting providers.
https://github.com/TwiN/gatus
-
-
prometheus-operator
Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
Project mention: Production-Ready GPU Inference Autoscaling on EKS with Karpenter, KEDA, and Dragonfly | dev.to | 2026-05-17kube-prometheus-stack – Prometheus Operator, Grafana, and Alertmanager for Kubernetes; provides the metrics that drive KEDA scaling
-
Project mention: AI Alert Assistant: How n8n + LLM Replace Routine Diagnostics | dev.to | 2026-03-23
Prometheus + Alertmanager
-
Scrutiny monitors my HDD/SSD for temperatures, errors, and more, with a clean web UI.
-
coroot
Coroot is an open-source observability and APM tool with AI-powered Root Cause Analysis. It combines metrics, logs, traces, continuous profiling, and SLO-based alerting with predefined dashboards and inspections.
Coroot is an Apache 2.0 open source platform that simplifies observability with no-code configuration. The Coroot node-agent already collects CPU profiles for any process on the node using eBPF, with zero integration from the application side. For Java, we dynamically inject async-profiler into the JVM to get memory and lock profiles. But Go processes were still a blind spot for non-CPU profiling unless the app exposed a pprof endpoint and the cluster-agent scraped it.
-
Project mention: The Complete Guide to AWS Service Monitoring with OpenTelemetry (2026) | dev.to | 2026-05-19
OpenTelemetry (OTel) is a CNCF-graduated open-source project. It provides a unified standard for collecting metrics, logs, and traces from distributed systems. At its core, OTel consists of three things:
-
WatchYourLAN
Lightweight network IP scanner written in Go. With notifications, history, export to Grafana
-
Project mention: Three Budget-Guardrail Failure Modes That Matter More Than Model Quality (May 2026) | dev.to | 2026-05-19
Source: https://github.com/opencost/opencost/issues/3533 (open, updated 2026-04-06)
-
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
Go Monitoring discussion
Go Monitoring related posts
-
Rate Limiting in Spring Boot REST APIs: Bucket4j + Redis
-
Mqtt-dashboard – A self-hostable MQTT dashboard/explorer for IoT developers
-
Chronos vs Toto: Zero-Shot Forecasting Benchmark Results
-
The Complete Guide to AWS Service Monitoring with OpenTelemetry (2026)
-
Launch HN: Superlog (YC P26) – Observability that installs itself and fixes bugs
-
Kubecost Explained: Kubernetes FinOps That Moves the Bill
-
Production-Ready GPU Inference Autoscaling on EKS with Karpenter, KEDA, and Dragonfly
-
A note from our sponsor - SaaSHub
www.saashub.com | 6 Jun 2026
Index
What are some of the best open-source Monitoring projects in Go? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | prometheus | 64,324 |
| 2 | glance | 34,855 |
| 3 | cilium | 24,441 |
| 4 | beszel | 22,437 |
| 5 | bettercap | 19,385 |
| 6 | cadvisor | 19,179 |
| 7 | ctop | 17,685 |
| 8 | Telegraf | 17,603 |
| 9 | VictoriaMetrics | 17,104 |
| 10 | sampler | 14,570 |
| 11 | thanos | 14,092 |
| 12 | nightingale | 13,054 |
| 13 | pyroscope | 11,477 |
| 14 | gatus | 11,100 |
| 15 | nezha | 10,069 |
| 16 | prometheus-operator | 9,932 |
| 17 | alertmanager | 8,496 |
| 18 | scrutiny | 7,851 |
| 19 | coroot | 7,677 |
| 20 | opentelemetry-collector | 7,110 |
| 21 | WatchYourLAN | 7,025 |
| 22 | opencost | 6,558 |
| 23 | kube-state-metrics | 6,133 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com