Jump to: navigation, search

Difference between revisions of "Large Scale SIG/Monitor"

Line 11: Line 11:
== Resources ==
== Resources ==
* oslo.metrics [code https://opendev.org/openstack/oslo.metrics/] and [documentation https://docs.openstack.org/oslo.metrics/latest/]
* oslo.metrics [https://opendev.org/openstack/oslo.metrics/ code] and [https://docs.openstack.org/oslo.metrics/latest/ documentation]
* Learn about golden signals (latency, traffic, errors, saturation) in the [https://sre.google/sre-book/monitoring-distributed-systems/#xref_monitoring_golden-signals Google SRE book]

Revision as of 14:04, 24 November 2020

The second stage in the Scaling Journey is Monitor.

Once you have properly configured your cluster to handle scale, you will need to properly monitor it for signs of load stress. Monitoring in OpenStack can be a bit overwhelming and it's sometimes hard to determine how to meaningfully monitor your deployment to get advance warning of when load is just too high. This page aims to help answer those questions.

Once meaningful monitoring is in place, you are ready to proceed to the third stage of the Scaling Journey: Scale Up.


Q: How can I detect that RabbitMQ is a bottleneck ?


Other SIG work on that stage