What’s new in Prometheus monitoring for Docker and Kubernetes

Posted on 08-11-2017 , by: admin , in , 0 Comments

Prometheus, the open source monitoring system for Docker-style containers running in cloud architectures, has formally released a 2.0 version with major architectural changes to improve its performance.

Among the changes that have landed since the release of version 1.6 earlier this year:

  • An entirely new storage format for the data accumulated by Prometheus.
  • A new way for Prometheus to handle “staleness,” i.e. problems resulting when data reported by Prometheus doesn’t match the actual state of the cluster.
  • A method for taking efficient snapshot backups of the entire database.

Most of the changes shouldn’t force experienced Prometheus users to retool their environments. The new features are meant to work under the hood, without significantly altering workflow, although there are a few breaking changes (documented here).

New in Prometheus 2.0: More efficient time-series database storage format

Under the hood, Prometheus is a time-series database—a system for gathering statistics about running containers and storing them in a way that’s indexed by timestamps. Because time-series data arrives at high speed and from many sources, it’s hard to aggregate properly. Writing the data to disk becomes a major bottleneck.