Skip to content
Open
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 60 additions & 0 deletions documentation/docs/alert/alert_status.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
# View alert status by node or service

Use the **Alert Status** page to see all active alerts for a node or service in one place, check their states, and silence them without switching views.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Align the introduction with the silencing workflow.

Line 3 says users can silence alerts without switching views. Lines 45-47 say PMM opens the Silences page. Update the introduction to describe starting the silencing workflow, or change the steps to match the actual UI behavior.

Also applies to: 45-47

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@documentation/docs/alert/alert_status.md` at line 3, Align the Alert Status
introduction with the documented silencing workflow: update the statement near
“Alert Status” to say users start the silencing process there, or revise the
steps around the Silences page so they remain consistent with the existing
introduction.


This page is only available when Percona Alerting is enabled. To check, go to **Configuration > Settings > Advanced settings**.


## Check alerts for a specific node

To see all alerts affecting a single node:
{.power-number}

1. Go to **Alerts > Status**.
2. Toggle **Group by node** in the toolbar.
3. Find your node and expand it to see its individual alerts and their states.

## Filter alerts by state

Use the **State** dropdown in the toolbar to show only alerts in a specific state: **Normal**, **Pending**, **Firing**, **Recovering**, **No Data**, **Error** or **Silenced**.
Comment thread
coderabbitai[bot] marked this conversation as resolved.

## Check alerts for a specific service

To filter the alert list by service:
{.power-number}

1. Go to **Alerts > Status**.
2. Click **Show/Hide filters** in the toolbar to reveal the column filters.
3. In the **Service** column filter, enter the service name.

The table updates to show only alerts associated with that service.

## Get details on an alert

Click any alert row to open the details pane. From here you can:

- **See what triggered the alert**: the **Details** tab shows the summary, description, state and duration, node, service, severity, triggered at timestamp, and the MetricsQL expression. Check **Rule configuration** to see evaluation settings, template name, folder, and rule health.
- **Debug custom templates or verify label values**: switch to **Raw data** to inspect the full label set and JSON payload.
- **Move between alerts**: use the arrow buttons in the pane header to go to the next or previous alert without closing the pane.

## Silence an alert

You need **Editor** role or higher to silence alerts.
{.power-number}

1. Click the actions menu on the alert row.
2. Click **Silence**. PMM opens the **Silences** page with the alert labels pre-filled.
3. Set the duration and confirm.

Silenced alerts stay visible in the table with a **Silenced** badge. To unsilence, open the actions menu and click **Unsilence**.

## Make custom alerts appear in this view

Built-in PMM alert templates automatically include the labels that this page uses to group alerts by node and service.

If your custom templates do not show up correctly, add these labels to the template definition:

- `node_name`: identifies the monitored node.
- `service_name`: identifies the monitored service.

For instructions, see [Alert rules and alert templates](../alert/templates.md).
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Outdated
2 changes: 1 addition & 1 deletion documentation/docs/release-notes/3.9.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -259,7 +259,7 @@ To lower your exposure in the meantime:
- [PMM-15114](https://perconadev.atlassian.net/browse/PMM-15114): Fixed the **Scanned and Moved Objects** panel in the **MongoDB Instance Summary** dashboard showing blank labels in the legend instead of the operation type (`scanned`, `scanned_objects`).


## Known issues
## 🔶 Known issues

### UI upgrade progress bar stops when upgrading to PMM 3.9.0 ([PMM-15266](https://perconadev.atlassian.net/browse/PMM-15266))

Expand Down
2 changes: 2 additions & 0 deletions documentation/mkdocs-base.yml
Original file line number Diff line number Diff line change
Expand Up @@ -395,10 +395,12 @@ nav:
- Percona Alerting:
- alert/index.md
- alert/alert_rules.md
- alert/alert-status.md
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Outdated
- alert/contact_points.md
- alert/templates_list.md
- alert/silence_alerts.md
- alert/disable_alerts.md

- Back up and restore:
- backup/index.md
- backup/prepare_storage_location.md
Expand Down