Understanding and Acting on Alerts

When an alert fires

Merlonix raises an alert when a monitored asset has a problem — an SSL certificate expiring or invalid, a DNS change, a site down, a heartbeat missed, and so on. Alerts are delivered to your notification channels based on their severity (see "Notification Channels").

Alert states

• Open — fired and not yet handled.
• Acknowledged — you have seen it; it stays visible but is marked as being worked on.
• Muted / snoozed — suppressed for a chosen time; still shown in the dashboard, external notifications silenced during the window.
• Resolved — closed. This is final; a resolved alert cannot be reopened.

What you can do

On the Alerts page (/app/alerts/) each alert has actions:

• Ack (acknowledge) — available while the alert is open.
• Snooze — pick 30 minutes, 2 hours, 4 hours, or 1 day; suppresses notifications while it stays open.
• Resolve — close it once the underlying issue is fixed.

The list updates live as new alerts fire, and you can filter by status (open, acknowledged, muted, resolved) and severity (critical, warning, info).

Reducing noise

If an asset is alerting too often, see "False Alerts and How to Tune Them", set a maintenance window for planned work (see "Maintenance Windows"), or let Merlonix suppress alerts automatically during a known vendor outage (see "How Vendor Status Monitoring Works").