---
title: "Find all investigations of the same alert | Proofline Help"
description: "Open the Investigations tab when you want to compare repeated firings of one alert in an environment. The list can group several investigations under one symptom."
url: https://proofline.sh/help/investigation-one-alert-history/
---

[Help center](/help/)

# Find all investigations of the same alert

Open the Investigations tab when you want to compare repeated firings of one alert in an environment. The list can group several investigations under one symptom.

[![The Production Investigations list shows alert and question investigations with their state, such as Running, Ranked leads, Incomplete and Likely cause, and when each was received, in the fictional Northstar Demo workspace.](/help-images/environment-investigations-light.png)](/help-images/environment-investigations-light.png)

Each investigation names what started it and how it ended. Fictional demo workspace.

## Expand or filter the alert’s history

When the same alert opens several times in a row, the list shows one row for them, such as **Opened 9 times, 6 hours ago to 1 day ago**, with the newest symptom. Select the row to list every opening of that alert. The count reads **Opened at least** when the openings reach the end of a page that has older pages, because more may follow there. It also reads **Opened at least** on the first row of an older page when those openings continue from the page before, even when only one opening is left (**Opened at least once**). Alerts are matched by their Cloud Monitoring policy, CloudWatch alarm or Sentry issue, or by their Azure Monitor alert rule and the resources it targets, so two alerts that share a name keep separate rows. When a Cloud Monitoring policy alerts separately for each resource or metric label value, each of those is its own alert, with its own row. So is each dimension value of an Azure Monitor metric alert rule split by a dimension, such as each API name. A log search alert rule stays one alert even when it is split by a dimension.

You can also open an investigation that a Cloud Monitoring alert, a CloudWatch alarm, a Sentry issue alert or an Azure Monitor alert started, and select **Other investigations of this alert**. The list then shows only the investigations that the same alert, matched as above, started in this environment, under the alert's name. A rerun is not listed again. Select **Show all investigations** to return to the whole list.

Questions and some older alert investigations have no such link.

## Related guides

-   [Find an environment's investigations](/help/environment-investigations/)
-   [Create an environment](/help/create-environment/)
