[HN Gopher] How the open source Caddy server uses Grafana Cloud ...
___________________________________________________________________
How the open source Caddy server uses Grafana Cloud for full-stack
observability
Author : m_sahaf
Score : 21 points
Date : 2024-02-21 18:30 UTC (4 hours ago)
(HTM) web link (grafana.com)
(TXT) w3m dump (grafana.com)
| ttymck wrote:
| I'd have preferred more technical details. But it's interesting
| to get a sense of the rather "cowboy" (in a positive sense)
| approach of the caddy maintainers for their "online" service
| offering (a build server).
| m_sahaf wrote:
| > I'd have preferred more technical details.
|
| There isn't much technical details to it. Caddy exposes
| profiles by default[0] and prometheus metrics are available as
| opt-in. We set up grafana-agent to collect profiles and metrics
| from Caddy, poked at the Grafana Cloud portal, studied the
| available data, and checked the charts for anomalies. Grafana
| Cloud made it easy for us to get started with that without
| having to build more infrastructure for them, which will also
| require extra energy that can be better spent on the core of
| our project.
|
| [0]
| https://twitter.com/MohammedSahaf/status/1760415991513637137
| starkparker wrote:
| The biggest problem in the observability space is people
| assuming that other people know what any of this entails.
|
| What "isn't much technical details" to you is required
| information for way more people than o11y wonks (not you, but
| more Grafana Cloud and some OTEL champions etc.) seem to
| believe, especially around cloud/microservice metrics.
|
| Prometheus and PromQL especially are opaque and hard to start
| using. The bar of entry to understanding how it can solve
| problems is higher than it looks from the inside, especially
| when you have account managers in your ear making sure _you_
| know.
___________________________________________________________________
(page generated 2024-02-21 23:01 UTC)