Skip to main content

Anomalies notifications in Container Observability

Container Observability observes the behavior of Microservices and notifies the affected entity by detecting anomalies within the cluster.

The following table depicts the identification of anomalies detected by Container Observability:

Map

Anomaly representation

Status

Node Map

2690385599

The anomaly is represented for pods and containers hosted in a Node that needs immediate attention. The incident tickets are generated in the Alerts.

Apps Map

2690389829

This represents an anomaly issue of a service in Apps Map that needs immediate attention. The user can refer to incident tickets generated in the Alerts.

Kubernetes Map

2690383953

Represents an anomaly for a node in the K8s cluster that needs immediate action, user can refer to the Alert ticket for Node in the Alerts.

Trace Map

2690386586

Represents the anomaly due to an increase or decrease of response time by any of the services in the path. Container Observability triggers an alert notification, and users can refer to the ticket generated in the Alerts.

Related topics: