3 ms·
Speaking as a Prometheus developer, each is suited to different things. For example if you want to store timeseries data long term and already use HBase then O
by bbrazil 10y ago
Speaking as a Prometheus developer, each is suited to different things.
For example if you want to store timeseries data long term and already use HBase then OpenTSDB is a good choice.
On the other hand if you want to do monitoring that's simple and dependable in an emergency with querying, graphing and alerting over short/medium-term data, then Prometheus would a good choice.
- pmahoney 10y ago> short/medium-term data This in particular, but your entire post, would be a great addition to the Prometheus front page, or top of the documentation section. This wasn't clear to me initially, speaking as someone who evaluated prometheus a few months ago.
- bbrazil 10y agoWe plan on seamlessly integrating with long-term storage (https://prometheus.io/docs/introduction/roadmap/#long-term-storage https://prometheus.io/docs/introduction/roadmap/#long-term-s...) and OpenTSDB is one option for that for us. Ignoring that as it's planned work, the typical considerations are more around availability vs. consistency and that we're a metrics system focused on operations rather than a event store. Most of that's already covered in our docs. See https://prometheus.io/docs/introduction/overview/#when-does-it-fit https://prometheus.io/docs/introduction/overview/#when-does-... and https://prometheus.io/docs/introduction/faq/ https://prometheus.io/docs/introduction/faq/