Rule-based Alert
In the Detect panel, you can view a summary of the rule-based alert specific to the container:
 |
Details of the anomaly, Type, and Category of the alert.
The description explains the cause of an anomaly:
Click > to expand the Target that represents details of the affected entity and its dependencies that might be the cause of the anomaly.
Click > to expand Anomaly Condition to list the following details:
State of the anomaly with the first occurrence and recent occurrence time with other details.
On the right side of the Detect panel, you can also view:
The history of logs, metrics, events, and configuration details to analyze the previous behavior of the affected container.
Quick links to analyze the past behavior of the container are Logs, Metrics, Events, Configs, and Dashboard. Previous logs for the following:
Container: The state of the container listed in detail from the time of anomaly occurred.
Pods: The state of pods in which the container is hosted.
Nodes: The state of nodes in which the pods are hosted.
From each alert ticket, you can compare the current metric data with the previous metric through the following quick links:
Configs: You can view or download the YAML file for configuration details of the particular entity deployment.
Application state: To identify the state of containers.
Metrics history: To determine the previous metric health of containers recorded at each time interval.
Events history: To determine the history of events that are created due to a state in the cluster due to container impact such as (failing, restarting, re-scheduling, or exceeding memory of the container).
Dashboard
Service performance: It describes the performance of each service in terms of traffic inbound and outbound, request count, and latency from one particular service to its dependent services (such as you can visualize the performance of the container and its dependent services).
Related topics: