4 ms·
If you prefer running an open-source solution yourself, Prometheus (http://prometheus.io/ http://prometheus.io/) addresses exactly those points and works especi
by jrv 11y ago
If you prefer running an open-source solution yourself, Prometheus (http://prometheus.io/ http://prometheus.io/) addresses exactly those points and works especially well in a dynamic cloud / microservices / container scheduler world.
It has a dimensional data model, a powerful query language to go with it, and covers aspects from instrumentation to storing data, all the way to alerting and dashboarding. The latest version of Grafana has native Prometheus support now too. Many tools (like Kubernetes or etcd) already export Prometheus metrics natively, so you can monitor them with Prometheus right out of the box. Support for many kinds of service discovery (Kubernetes, Marathon, EC2, Consul, ...) make it work very well to monitor dynamically scheduled services as well. Disclaimer: Prometheus author.
- js2 11y agoI chose InfluxDB about a year ago because it was the only option that allowed me to put each individual event into a time series and then do the grouping/counting after the fact. The prometheus docs used to say this it wasn't suited to that use case. Is that still the case? edit: yup, the prometheus docs indicate InfluxDB is better suited to this use case. http://prometheus.io/docs/introduction/comparison/ http://prometheus.io/docs/introduction/comparison/ Aside, I really appreciate this comparison page and the prometheus docs in general are well done.
- jrv 11y agoYes, Prometheus is fundamentally a store for numeric time series (with a set of dimensions attached), not a store for individual events or log entries.