We are happy to announce that as of today, Prometheus graduates within CNCF.
We are happy to announce that as of today, Prometheus graduates within the [CNCF](https://www.cncf.io/).
Prometheus is the second project ever to make it to this tier.
Prometheus is the second project ever to make it to this tier.
By graduating Prometheus, CNCF shows that it's confident in our code and feature velocity, our maturity and stability, and our governance and community processes.
By graduating Prometheus, CNCF shows that it's confident in our code and feature velocity, our maturity and stability, and our governance and community processes.
This also acts as an external verification of quality for anyone needing this for their internal Q&A.
This also acts as an external verification of quality for anyone in internal discussions around choice of monitoring tool.
Since reaching incubation level, a lot of things happened; some of which stand out:
Since reaching incubation level, a lot of things happened; some of which stand out:
* We redid our storage back-end to support high churn in services
* We completely rewrote our storage back-end to support high churn in services
* We had a large push towards stability, with 2.3.2 having no known bugs or issues
* We had a large push towards stability, with 2.3.2 having only onw known bug
* We started a documentation push with a special focus on making Prometheus adoption and joining the community easier
* We started a documentation push with a special focus on making Prometheus adoption and joining the community easier
Especially the last point is important as we currently enter our fourth phase of adoption. These phases were adoption by
Especially the last point is important as we currently enter our fourth phase of adoption. These phases were adoption by
# Monitoring-centric users actively looking for the very best in monitoring
1. Monitoring-centric users actively looking for the very best in monitoring
# Hyperscale users facing a monitoring landscape which couldn't keep up with their scale
2. Hyperscale users facing a monitoring landscape which couldn't keep up with their scale
# Companies from small to Fortune 50 redoing their monitoring infrastructure
3. Companies from small to Fortune 50 redoing their monitoring infrastructure
# Users lacking funding and/or resources to focus on monitoring, but hearing about the benefits of Prometheus from various places
4. Users lacking funding and/or resources to focus on monitoring, but hearing about the benefits of Prometheus from various places
Looking into the future, we anticipate even wider adoption and remain committed to handling tomorrow's scale, today.
Looking into the future, we anticipate even wider adoption and remain committed to handling tomorrow's scale, today.
Richard Hartmann <richih@richih.org>