---
title: "Trace the incidents joined to a Cloud Monitoring investigation | Proofline Help"
description: "Open Evidence on an investigation that started with Cloud Monitoring. A single investigation can include several incidents that opened while it was running."
url: https://proofline.sh/help/investigation-cloud-monitoring-incidents/
---

[Help center](/help/)

# Trace the incidents joined to a Cloud Monitoring investigation

Open Evidence on an investigation that started with Cloud Monitoring. A single investigation can include several incidents that opened while it was running.

## Match incidents, Slack messages and telemetry

When an alert policy opens another Cloud Monitoring incident while its investigation is still running and less than 10 minutes old, the incident joins that investigation, so one investigation can cover several incidents. The header then counts them, and **Closes recorded** says how many of those incidents Cloud Monitoring has reported closed, such as **1 of 3 incidents**. **Original incident** shows the state of the incident that started the investigation; its close does not mean the other incidents closed. With one incident, **Alert** shows its state.

In **Evidence**, **Alert incidents** says how many incidents of the alert opened while the investigation was open, then whether Proofline's reads cover them. On a rerun, it counts and lists the incidents of the original investigation. Open **Incidents** under **Alert incidents** to list each incident with its link to Cloud Monitoring and, when Proofline received it, its close time. **No close recorded** means only that Proofline holds no close for that incident. It does not mean that the incident is still open, or that the service has recovered.

Under each incident, **Slack** names the Proofline message that first told the channel about it: the **First message**, or the **Concluded update** for an incident that joined after Proofline first posted, with its time and how long after the incident opened. **No delivery confirmed** means that Proofline holds no record of a message that named the incident; it does not show whether the channel heard about it. A rerun's incidents have no **Slack** row, because a rerun's message names none of them.

Under **Telemetry Proofline read**, each read of a joined incident names that incident by when it opened. A joined incident is associated with the investigation, which does not mean that Proofline read its telemetry; the sentence after the count under **Alert incidents** says which incidents the reads cover. **The reads cover all of them.** means that every joined incident got a read. When some got none, a sentence that starts with **Not read:** counts them and says why, such as that they arrived after the reads were chosen. **Which of them the reads cover was not recorded.** means that the investigation kept no record of which incidents its reads cover.

## Related guides

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