$EMPLOYER has a very sizable influx deployment and push the limits of the software (bursts of ~500k metrics per second in some cases). We are also in the process of moving virtually everything (including kapacitor, influx, etc) onto Kubernetes. That said, everything in the entire kubernetes ecosystem already includes prometheus exporter support builtin. Also, Tectonic (from CoreOS) has the most wonderful prometheus operator https://coreos.com/blog/the-prometheus-operator.html which lets each team trivially spin up prometheus to monitor all of their apps. It also lets each team spin up their own alertmanager to send alerts, with kubernetes guaranteeing the high availability.
Why is this useful? Prometheus is wonderful for ephemeral application state and monitoring, but isn't really meant for storing metrics longer term. Sometimes you want to look at the same metrics over a year or so. This is what Influx is built for. So you have prometheus for collecting metrics and monitoring your cluster, then you have it reading and writing to Influx. This is literally the best of both worlds. This will be a big deal going forward for our team.
