I often encounter a lot of confusion about push vs. pull and whether you should pick Prometheus or Influx.<p>Prometheus comes along every so often and scrapes metrics your program exposes via a very simple API. This has the advantage that your code doesn't need to know about some endpoint of some cluster, it just needs to buffer up and expose some info it knows about itself from the recent past.<p>You don't need to maintain a cluster of Prometheus either, you can just run more than one for redundancy (kind of like an active-active) - it is meant for relatively ephemeral information, it is efficient, and one big Prometheus node will probably do you fine.<p>Where to store compacted historical metrics (less coarse resolution, still interesting data that you might not want to throw away) and how has been an open question. Sinking it into influx could be a good answer, so this is welcome news.
Congrats! Well done, seriously. I love it when things like this happen; settling on Prometheus as a standard will open access to so much more tooling.<p>(Which is also why I'm super excited to use timescale [<a href="http://www.timescale.com" rel="nofollow">http://www.timescale.com</a>] once grafana gets support for postgres!)