It's worth noting that Prometheus isn't distributed either. So OSS InfluxDB or that are the same in terms of distributed capabilities.

While Prometheus's built-in local storage is not distributed, we are in the process of implementing generic interfaces to allow Prometheus to talk to decoupled distributed, horizontally scalable, durable, remote storage (or even other non-storage systems like queues etc.). There will be several implementations sitting behind this interface in the end (see already Vulcan from DO and Frankenstein from Weaveworks, both experimental right now), depending on what you'd rather run and what fits your use case best.

Most importantly, Prometheus will never decide to exclude a feature for commercial reasons. As it's a 100% open-source and independent project not controlled by any single company, we don't have those kinds of incentives. We just want to build the best monitoring system. Note that we still say "no" to a lot of features, but that's only for technical reasons, to avoid bloat, or to keep the project maintainable.

Prometheus can be scaled with sharding and there are different solutions coming out to address this, like a proxy layer for queries.

See the PromCon 2016 videos for latest news on this.

The video is here: https://www.youtube.com/watch?list=PLoz-W_CUquUlCq-Q0hy53Tol...

And it's worth noting that dalmatiner magic relies on ZFS + riak. The ZFS part being problematic to run on linux.

There is currently no open source monitoring solutions that support more than a single node.

If you have serious infrastructure, you gotta move to the paid SaaS monitoring solutions which are ALL awesome.: https://www.datadoghq.com/ and https://signalfx.com/

Note: I am not affiliated with any of these services. I just have a very strong interest in nagios/icinga/riemann/graphite/grafana dying since my painful experience of setting up and maintaining them.

We're looking into Cyanite as an alternative. It speaks the various Graphite protocols and feeds data into Cassandra, which takes care of the HA concerns. I haven't built it yet but I'm fairly certain we can run it in Kubernetes to make the entire stack HA.

http://cyanite.io

We dropped InfluxDB after they introduced their enterprise version. Currently, we are running several nodes of Riemann/Cyanite/Cassandra. It works very well, integration is pretty straight forward.

That stack would perform even better if you swapped ScyllaDB for Cassandra.

Do you have production experience with ScyllaDB?

I wanted to use this for a while. Can we consider it 100% compatible and can be used as a drop-in replacement?

I've not yet used in in production, but I have kicked the tires enough to know that a) it's (much) faster, and b) I'm planning a production deployment this fall.

For the most part it's compatible with Cassandra out-of-the-box, i.e. many well-known frameworks that run on top of Cassandra "just work". The main thing it's missing is support for Lightweight Transactions (scheduled for the 2.0 release).

The dev team behind ScyllaDB is rock solid, very competent.

You also have http://gnocchi.xyz