4 ms·
I have a love/hate relationship with Prometheus. If I had no budget for metrics its likely the thing I would reach for, but I’m dying for someone to open source
by kasey_junk 6y ago
I have a love/hate relationship with Prometheus. If I had no budget for metrics its likely the thing I would reach for, but I’m dying for someone to open source a ‘next level’ metrics system (something like Monarch or Circonus but free).
But woe betide the team that has to run it as a service. Not that other metrics systems are better but Prometheus can be brutal in that space.
As a ‘squad level’ tool its really good. After that it gets hairy fast.
- deleted 6y ago[deleted]
- RhodesianHunter 6y ago>I’m dying for someone to open source a ‘next level’ metrics system For the time being this is a "full team working full 40 hour weeks for year(s)" problem, so I'd be shocked to see it done open source.
- roskilli 6y agoM3 is meant to be an open source, central, horizontally scalable metrics store - but your mileage may vary. Either way, check it out: https://m3db.io https://m3db.io
- valyala 6y agoCould you give more context on Monarch or Circonus features that are missing in Prometheus? BTW, I'm working on VictoriaMetrics - open source monitoring solution that works out of the box. See https://github.com/VictoriaMetrics/VictoriaMetrics https://github.com/VictoriaMetrics/VictoriaMetrics
- kasey_junk 6y ago1) histograms as the basic primitive. 2) bidirectional transport 3) runtime configurable filtering at source, collection and sync. 4) provenance as part of the transport.