# Acknowledge and resolve an alert

> Take an open alarm so others know you are on it, look at what happened around it, then close it with a note on how it was fixed.

Source: https://proxus.io/docs/monitor/acknowledge-an-alert

At the end of this guide the alarm is closed as **Resolved**, with your name and a note on the fix, and it no
longer appears in **Needs attention**.

## Before you start

- An open alarm. It appears in the [Operations Center](https://proxus.io/docs/monitor/operations-center) under **Needs attention**
  and in **Monitor > Alerts**.
- A user role that may change alarms.

## Take the alarm

Acknowledge an alarm as soon as you start working on it. Others then see that it is in follow-up and who has it.

1. Open **Monitor > Operations Center**.
2. Find the alarm in **Needs attention**.

*Screenshot: An open alarm in Needs attention with the WARN badge, the time since it was raised marked unacknowledged, and the Acknowledge and Open buttons*

1. The level: **CRIT**, **WARN** or **NOTE**.
2. How long it has waited. It turns red after 15 minutes without anyone taking it.
3. **Acknowledge** takes it from here.
4. **Open** opens the alarm page.

3. Select **Open** to read the alarm first, or **Acknowledge** to take it straight away.

On the alarm page, **What happened** shows the reason, the device and the condition, and **Around the alarm** shows
the tag's values and the machine state before and after the moment it fired. **Changed before** tells you whether
someone changed a device, rule or gateway shortly before. See [Alerts](https://proxus.io/docs/monitor/alerts).

4. Select **Acknowledge** in the toolbar.

*Screenshot: The alarm page after acknowledging: status Acknowledged in the header and Acknowledged by Admin in the timeline*

1. The status is now **Acknowledged**.
2. The timeline shows who acknowledged it and when.

The alarm leaves **Needs attention** and is listed under **… acknowledged, in follow-up**.

> **Note:**
For an alarm raised by a rule, a new match after you acknowledged it raises a new alarm. For an alarm raised by a
pipeline, new matches are counted on the acknowledged alarm until it is closed.

## Close the alarm

When the cause is fixed:

5. On the alarm page, select **Resolve**.
6. In **How was it fixed?**, describe what you did. The field is required.
7. Select **Resolve**.

*Screenshot: The Resolve alarm dialog with the fix described in How was it fixed? and the Resolve button*

1. **How was it fixed?** The text is kept with the alarm as **Solution**.
2. **Resolve** closes the alarm.

If the alarm needs no action (a test, a known event), select **Ignore** instead and confirm. An ignored alarm is
closed without a note. Neither a resolved nor an ignored alarm can be reopened.

To handle several alarms at once, tick them in **Monitor > Alerts** and use the same actions from the toolbar.

## What's next

- [Alerts](https://proxus.io/docs/monitor/alerts): statuses, levels and repeats.
- [Rule actions](https://proxus.io/docs/automate/rule-actions): send an email or a message when an alarm is raised.