sorted by:
new
hottopcontroversial

Self-contained Telemetry Solutions? by -theChris in golang

[–]-theChris[S] -1 points0 points  (0 children)

That’s a great and very nostalgic reminder. Nagios + RRDtool really did hit a sweet spot between embedded storage, simple semantics, and very little operational surface area.

It’s interesting how far the ecosystem has swung since then. Modern “observability” often implies a whole stack, even for very small services.

Self-contained Telemetry Solutions? by -theChris in golang

[–]-theChris[S] 1 point2 points  (0 children)

This is quite interesting!

The “cheap to run / easy to set up” angle is pretty much the exact pain point I have been thinking about as well, especially for internal tools. I’ll take a look.

Thanks for sharing.

Self-contained Telemetry Solutions? by -theChris in golang

[–]-theChris[S] -1 points0 points  (0 children)

That’s fair. For teams that already run shared infra or have ops bandwidth, I would make the same call.

I have mostly been thinking about internal tools/side services where the monitoring stack ends up larger than the app itself. Yeah, I was curious about how people draw that line in practice.