A month after 1.1.0, Prometheus 1.2.0 is out. Let's look at the changes.
Reliable Insights
A blog on monitoring, scale and operational Sanity
The Prometheus ecosystem contains a multitude of integrations, both officially supported and third party. Let's have a look at how to use the mysqld_exporter.
Python is one of the four languages that has an official Prometheus client. Let's take a quick look at how to use it.
We've already looked at how to setup Slack with the Alertmanager, and saw the default notification. Wouldn't it be nice to customise it?
The Prometheus instrumentation guidelines say to use seconds, and the timing functions in client libraries follow this. Why?
It can seem like a good idea to use recording rules to make more explicit the content of a time series, particularly for those not used to labels. However this usually leads to confusing names and losing the benefits of labels.
I've previously mentioned that you shouldn't have the version of your software as either a target label, or exposed via a label on all metrics of your server as it'll make using the metrics more challenging. What should you do instead?
In a previous post I said that rather than adding another label such as host or alias to a target to give it a useable name, you should instead change the instance label. Let's see how you do that.
How you choose to name metrics is important. If everyone choose different schemes it'd lead to confusion, irritation and prevent us from sharing and reusing each others' work. I'd like to share some guidelines to help keep things sane for everyone.
