Red Hat officially supports the Cluster Observability Operator on OpenShift 4.17 clusters, and this article provides a quick overview to help you determine if the COO is right for your needs.

Rhdev is a blog and resource hub dedicated to Ruby on Rails development, a popular web application framework written in Ruby. Developers can explore tutorials, best practices, and case studies for building web applications with Ruby on Rails. Additionally, Rhdev covers topics such as ActiveRecord ORM, RESTful APIs, and frontend integration using JavaScript frameworks, offering insights for both beginners and experienced Rails developers.

Red Hat Developer

The Cluster Observability Operator (COO) is an optional component for Red Hat OpenShift designed to create and manage customizable monitoring stacks. It updates independently from OpenShift, allows deployment of multiple monitoring stacks, and is ideal for multi-tenant environments. COO provides enhanced monitoring capabilities compared to the default OpenShift monitoring system, including detailed Prometheus metrics, extended data retention, and customization options. It is suitable for enterprise users, operations teams, and development teams requiring advanced monitoring and long-term data analysis.

Brief overview of Cluster Observability Operator

What is the Cluster Observability Operator (COO)?

What is the difference between OpenShift default monitoring stack and COO?

Who should use Cluster Observability Operator?