Inspections | Coroot Documentation

📄️Overview

When you look at any dashboard, you are mentally evaluating whether the metrics are within their acceptable range of values or not.

These inspections allow you to monitor the Availability and Latency SLOs (Service Level Objectives) for every application.

This inspection detects when one or more instances of an application are not available or have been restarted.

This inspection detects situations in which an application is experiencing a lack of CPU time,

Coroot provides real-time visibility into GPU usage across your applications, helping you understand performance bottlenecks,

These memory inspections identify problems with the application's memory:

This inspection identifies issues related to the storage volumes used by the application.

This inspection detects network issues between the application and the services on which it depends.

This inspection highlights when your application logs deserve attention because they contain ERROR or WARNING messages.

The following inspections are based on the JVM metrics automatically collected by coroot-node-agent for each JVM running on the node.

This inspection relies on .NET runtime metrics automatically collected by coroot-node-agent for every .NET runtime running on the node.

This inspection monitors the additional latency in a Python application caused by GIL (Global Interpreter Lock) contentions.

Coroot inspects Postgres clusters using metrics gathered by the

Coroot inspects MongoDB replica sets using metrics gathered by the

Coroot inspects MySQL instances using metrics gathered by the

This inspection identifies issues with the availability and latency of Memcached instances.

This inspection identifies issues with the availability and latency of Redis instances.

Coroot automatically discovers and monitors every application rollout in your Kubernetes cluster.