veneur
docs
veneur | docs | |
---|---|---|
2 | 6 | |
1,714 | 625 | |
0.1% | 0.3% | |
3.5 | 8.4 | |
about 1 month ago | 12 days ago | |
Go | SCSS | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
veneur
-
OpenTelemetry in 2023
This was the idea behind Stripe's Veneur project - spans, logs, and metrics all in the same format, "automatically" rolling up cardinality as needed - which I thought was cool but also that it would be very hard to get non-SRE developers on board with when I saw a talk about it a few years ago.
https://github.com/stripe/veneur
-
Launch HN: Opstrace (YC S19) – open-source Datadog
One pain point with Prometheus is that is has relatively weak support for quantiles, histograms, and sets[1]:
- Histograms require manually specifying the distribution of your data, which is time-consuming, lossy, and can introduce significant error bands around your quantile estimates.
- Quantiles calculated via the Prometheus "summary" feature are specific to a given host, and not aggregatable, which is almost never what you want (you normally want to see e.g. the 95th percentile value of request latency for all servers of a given type, or all servers within a region). Quantiles can be calculated from histograms instead, but that requires a well-specified histogram and can be expensive at query time.
- As far as I know, Prometheus doesn't have any explicit support for unique sets. You can compute this at query time, but persisting and then querying high-cardinality data in this way is expensive.
Understanding the distribution of your data (rather than just averages) is arguably the most important feature you want from a monitoring dashboard, so the weak support for quantiles is very limiting.
Veneur[2] addresses these use-cases for applications that use DogStatsD[3] by using clever data structures for approximate histograms[4] and approximate sets[5], but I believe its integration with Prometheus is limited and currently only one-way - there is a CLI app to poll Prometheus metrics and push them into Veneur, but there's no output sink for Veneur to write to Prometheus (or expose metrics for a Prometheus instance to poll).
It would be extremely useful to have something similar for Prometheus, either by integrating with Veneur or implementing those data structures as an extension to Prometheus.
[1] https://prometheus.io/docs/practices/histograms/
[2] https://github.com/stripe/veneur
[3] https://docs.datadoghq.com/developers/dogstatsd/
[4] https://github.com/stripe/veneur#approximate-histograms
[5] https://github.com/stripe/veneur#approximate-sets
docs
-
OpenTelemetry in 2023
Prometheus text exposition format is de-facto standard used in monitoring. It would be great building an official observability standard on top it. This format is much easier to debug and understand than OpenTelemetry for metrics. It is also more efficient, e.g. it requires less network bandwidth and less CPU for transfer than Otel for metrics.
[1] https://github.com/prometheus/docs/blob/main/content/docs/in...
-
Kubernetes prometheus metrics for running pods and nodes?
I've set up prometheus to monitor kubernetes metrics by following the prometheus documentation.
-
Minimal, allocation-free OpenMetrics implementation for no-std/embedded Rust
It was added back to Prometheus.
https://github.com/prometheus/docs/blob/main/content/docs/in...
-
What is promeetheus monitoring?
Exporters are third-party tools that send metrics to the Prometheus server. When Prometheus cannot access metrics, it uses exporters. These exporters export metrics from systems and send the metrics to the Prometheus server. There are official and non-official exporters in Prometheus' GitHub organization.
-
Energy monitor exporter?
Now I'm looking for another energy monitor and I'm really struggling to find one! https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exporters.md
-
Monitoring Rust web application with Prometheus and Grafana
Metrics are exposed in a simple text-based format.
What are some alternatives?
opstrace - The Open Source Observability Distribution
flight-manual.atom.io - 📖 Documentation for Atom, generated by nanoc, hosted by GitHub Pages
cortex - A horizontally scalable, highly available, multi-tenant, long term Prometheus.
community - OpenTelemetry community content
Cortex - Cortex: a Powerful Observable Analysis and Active Response Engine
windows_exporter - Prometheus exporter for Windows machines
loki - Like Prometheus, but for logs.
rust-prometheus - Prometheus instrumentation library for Rust applications
influxdb-apply - Define InfluxDB users and databases with a yaml file.
terraform-aws-jaeger - Terraform module for Jeager
b3-propagation - Repository that describes and sometimes implements B3 propagation
prometheus - The Prometheus monitoring system and time series database.