| Title | Alert message or headline. It includes a clickable link to the alert detail page. |
| Severity | Indicates urgency. Examples: Critical, Warning, Info, Unspecified, or icons/colors. Helps prioritize response. |
| Status | Lifecycle stage of the alert:• New – Not yet handled• Acknowledged – Someone has just started working on it• Triaged – Someone has debugged the alert• Escalated – It has been escaled to the senior engineer• Remediated/Resolved – The issue has been resolved permanently or temporarily• Hidden – Manually snoozed or ignored |
| Type | Origin system for the alert (e.g., Rollbar, custom_bot, hipctl). |
| Channel | Slack channel of the alert (#logs, #monitoring, etc.). |
| Timestamp | When the alert was triggered. Useful for time-based debugging. |
| Actions | Contextual actions available per alert (explained below). |