Check whether an investigation added a PagerDuty note
Open the alert investigation to check its note status. Match the Cloud Monitoring incident that started the investigation to the open PagerDuty incident before expecting a note.
Match incidents and read the note result#
The note opens with the likely cause and the timeline entries that cite it, or, without one, with how many changes Proofline ranked and that a cause was not established. A note from a cancelled investigation says The investigation was cancelled before it finished. in place of that, and one from an investigation that stopped after repeated failures says The investigation stopped after repeated failures. The leads in such a note come from a run that did not finish. The note lists the leads in at most ten lines, says how many more are on the investigation page, and links to the investigation. It names no repository or commit SHA; those stay on the investigation page. The note is written once from the recorded result and is not updated later. A rerun adds its own note, which opens by saying it is the newer result; the earlier note stays as it was.
Proofline finds the incident by its incident key: the oldest triggered or acknowledged PagerDuty incident whose incident key is gcp- followed by the Cloud Monitoring incident ID. Titles and times play no part, so an incident with another incident key gets no note, and neither does a resolved one. When several incidents of one alert policy joined the investigation, each incident's own PagerDuty incident gets the same note, for at most 25 incidents per investigation.
The investigation page header says what happened to the note:
- Note added to the PagerDuty incident: the PagerDuty incident that matched the alert received the note.
- No open PagerDuty incident matched this alert, so no note was added: no triggered or acknowledged incident carried the alert's incident key when Proofline looked.
- PagerDuty refused the note: PagerDuty rejected Proofline's lookup or note.
- PagerDuty did not answer, so no note was added: Proofline stopped before PagerDuty confirmed a note, for example after repeated attempts to reach PagerDuty failed.
When the investigation covers more than one incident, a second line counts them, such as PagerDuty notes added for 2 incidents, not for 1. Incidents past the limit of 25 count as not noted. While the note is being sent the header shows no PagerDuty line, and the page shows the outcome when it is recorded. None of these lines describes the state of the PagerDuty incident itself.