Responding to Alerts
Last updated
Last updated
The Alert List feature provides users with a comprehensive overview of all active alerts within their system. Users can efficiently search for specific alerts using the provided search bar. To access the alert list logs, navigate to the dashboard and locate the Alert List on the left sidebar, or hover over Home and select Alert List.
Acknowledge: Acknowledgment signifies that the assigned team has recognized the alert and is aware of its existence. This step indicates initial awareness and readiness to address the issue.
Resolve: Resolution indicates that the alert has been successfully addressed and resolved, restoring normal operations.
Users have two options for acknowledging and resolving alerts:
Bulk Selection: This option allows users to select and acknowledge or resolve multiple alerts simultaneously.
Specific Selection and Action: Alternatively, users can individually select alerts and apply acknowledgment or resolution actions as needed.
The Alert Log provides users with detailed insights into specific alerts detected within the system.
To delve deeper into a specific alert, simply click on the alert name. This action will redirect you to a dedicated page where you can explore all the details associated with the alert.
Following are the details included:
Alert ID: ebf47f03-e533-4803-b72a-12d3a3ebb43c - Unique identifier for the alert.
Alert Name: prod-bluejay-db_CPUUtilization_bluejay_alert - Descriptive title of the alert.
Alert Description: - Further information, explaining the nature or cause of the alert.
Status: Ok - Indicates whether the alert is resolved or acknowledged.
Alert Source: CloudWatch - Source or origin of the alert.
Application Service: Payments - Provides details about the application service, including contact information such as Service Email, Slack, On-Call Policy, and relevant team details.
Metric: CPUUtilization - Specific metric from thresholds triggering the alert.
Resource Details: prod-bluejay-db/AWS/RDS/prod-bluejay-db - Information about the resource type and environment associated with the alert.
Opened At: 5/1/2024, 6:42:33 AM - Timestamp indicating when the alert was first detected.
Assigned To: Hari Prashanth K R - User or team assigned to address the alert.
Assigned At: 5/1/2024, 6:42:34 AM - Timestamp indicating when the alert was assigned.
Acknowledged At: 5/1/2024, 6:42:45 AM - Timestamp indicating when the alert was acknowledged by the assigned team.
Close Date: 5/1/2024, 6:46:33 AM - Timestamp indicating when the alert was resolved or closed.
By accessing and reviewing these detailed alert logs, users can gain a comprehensive understanding of each alert's context, facilitating prompt and effective responses to system incidents.
The "Search" functionality allows users to quickly locate specific resources based on their name. Users can input the name of the resource they are looking for in the search bar to retrieve relevant results.
Additionally, users can further refine their search results using the "Advanced Filter" options. These filters include:
Filter by Service Name: This filter allows users to search for alerts using the application service name associated with the alerts.
Filter by Status: Users can filter alerts based on their status, with four available options:
Ok: Indicates that the alert has been acknowledged and resolved.
Alarm: Signifies that the alert is currently active and requires attention.
Acknowledge: Indicates that the alert has been acknowledged by a user but has not yet been resolved.
Insufficient Data: Indicates that the alert lacks sufficient data for evaluation.
Filter by Assigned To User: This filter allows users to search for alerts assigned to a specific user.
Alert Opened and Closed Date: Users can also filter alerts based on their opening and closing dates.
