Re:Vulcan: An API-compatible alternative to Prometheus
by skybrian on Thursday August 25, 2016 @12:59PM
(#12360583)
I'm guessing the Prometheus they mean is a time-series database. See: https://prometheus.io/
[ Parent
| on HN ]
Re:Vulcan: An API-compatible alternative to Prometheus
by andrewstuart2 on Thursday August 25, 2016 @01:24PM
(#12360769)
It's specifically a TSDB built for metrics and instrumentation. Basically intended to be Google's Borgmon for everybody else in the same way Kubernetes is essentially Borg for everybdoy else.
Re:Vulcan: An API-compatible alternative to Prometheus
by agentgt on Thursday August 25, 2016 @01:30PM
(#12360827)
It is more than TSDB because it has dimensions. Most metric systems (aka Graphite) are just: <time> <name> <number> <maybe unit>.
It is sort of nice to have dimensions for rollup/filtering instead of doing weird name mangling like graphite does. For example one might add a dimension of build # or release version to each metric.
Having a dimension like build # you could even effectively say if your releases are improving performance wise and graph it. TBH haven't done it yet but I think it would be useful instead of just manually doing it with time filtering.
Re:Vulcan: An API-compatible alternative to Prometheus
by zphds on Thursday August 25, 2016 @04:12PM
(#12362097)
We do this with telegraf + influxdb. It has support for tags in measurements where we add the release version among other metadata which we can then visualize in grafana with a simple group by in the query.
You can also shove in multiple related metrics as part of the same measurement.
https://docs.influxdata.com/influxdb/v0.13/write_protocols/l...