Monitors & detections

A calmer place for incident history

Find interruptions, share the watch and leave private context for your team.

Reviewed

Give each interruption its own space

Monitors stays focused on current health and configuration. A monitor with an open incident has a View open incident shortcut beside its actions. Its preview drawer still shows recent checks and trends; Open workspace incidents leads to the incident list.

Older Downtime history/Detections links redirect to the Resolved list. The mobile app continues to use its existing Detections screen.

  1. Open Incidents in your workspace navigation. Open shows confirmed interruptions that have not yet recorded recovery.
  2. Choose Resolved to browse recovered incidents, newest starts first. Use Load more incidents to continue through your available history.
  3. Select a monitor name or View incident to open its own detail page. Use Refresh for the latest recorded state; the view does not update continuously.

Read the recorded story

The detail page shows the monitor name, open or resolved state, recorded cause, start and recovery times, duration and a timeline of detection, acknowledgment when present, and recovery. Open duration is elapsed time at the last refresh, not a live timer.

Recovery is confirmed by monitoring results; there is no manual resolve control. Pausing a monitor does not resolve its open incident.

Give the incident a second pair of eyes

Acknowledgment means someone is looking into the interruption. It does not mean the monitor is healthy, stop monitoring, mute alerts or automatically publish a status update.

The first acknowledgment is kept. If teammates act together, or a response is lost and you retry, their original name and time are not overwritten. There is no edit or undo control. Once the incident recovers, its acknowledgment remains in the recorded story; an already recovered incident cannot receive a first acknowledgment.

Viewers, read-only support visits and members without Manage access cannot acknowledge incidents. Access is checked again when saving. Workspace suspension also blocks the action. The recorded name is a snapshot; later name changes or departure do not rewrite the event.

  1. An owner or admin with Manage access to the monitor opens an unacknowledged open incident and selects Acknowledge. This is available on every plan.
  2. The button shows progress while saving. A green confirmation and the recorded name/time show that the acknowledgment is safely on record.
  3. The Open list gets a small Acknowledged marker. Open the detail page to see who acknowledged it and when, alongside its recorded timeline. Use Refresh to pick up another teammate’s latest action.

Share the watch with a teammate

Assignment is available on every plan. Only an owner or admin with Manage access to the monitor can change it. Eligible assignees must also be active, email-verified owners or admins with Manage access to that monitor. Viewers and support visits are read-only.

Assignment, acknowledgment and recovery are separate. Assigning someone does not automatically acknowledge or resolve the incident, change monitor permissions, pause checks, mute alerts, publish a status update or send an email/push notification.

If a teammate loses membership, changes role, loses monitor access or becomes inactive, the recorded name stays in history. An open incident shows Needs a new lookout; choose another eligible person or explicitly clear it. Assignment never restores someone’s access.

Changes are version-checked. If another teammate saves a different choice first, close and reopen the picker before saving. Retrying the same saved choice does not create duplicate events. A recovered incident keeps its recorded assignment; new assignment changes are for open incidents only.

Recorded names and times are snapshots. Later account-name changes or departure do not rewrite earlier events. Only teammates who can view the monitor can view its private incident history. The mobile Detections screen does not yet offer assignment.

  1. Open an incident and find Share the watch. Choose Assign teammate, or Change beside an existing assignment.
  2. In the picker, choose an eligible teammate or Unassigned to clear the assignment, then select Save assignment. The shared search matches the choices already loaded; use More teammates if the person you need is not yet shown.
  3. The incident shows its recorded assignee, and its timeline records who assigned, changed or cleared the watch. Use Earlier assignment changes when an incident has a longer history.

Keep the impact in view

Unspecified means not assessed yet. Low means limited impact; Medium means noticeable impact; High means significant impact; Critical means widespread or business-critical impact. Your team chooses based on actual impact: monitoring does not automatically assign a level.

Severity is available on every plan. Only owners/admins with Manage access to the monitor can change an open incident. Viewers and read-only support can read the recorded level and history. Recovered incidents retain their assessment; their severity cannot be newly changed.

Severity does not acknowledge, assign, resolve or pause an incident, change check intervals, trigger or suppress notifications, reorder the list, or publish a public update. It is private response metadata; mobile Detections does not yet show severity.

If another teammate saves first, close the editor, select Refresh on the incident, then reopen the editor before choosing again. Repeating the same saved level does not duplicate history. Unspecified clears the assessment while retaining earlier changes. Names and times remain recorded after a teammate is renamed or leaves.

  1. Open an incident and find A sense of impact. Select Set severity, or Change severity beside an existing assessment.
  2. Choose Unspecified, Low, Medium, High or Critical, then Save severity. The list shows a small label for assessed incidents; Unspecified keeps the list quiet.
  3. Read the private timeline for who changed severity, when, and the previous and new levels. Use Earlier severity changes to load more.

Leave a little context for the next lookout

Notes are available on every plan, on both open and recovered incidents within your available history. Owners/admins with Manage access to the monitor can add notes; viewers and read-only support can read them where they have monitor access. Workspace suspension blocks new notes.

Use notes for checks performed, findings and handover context. Plain text keeps the story readable: HTML and Markdown are not rendered, and links are not automatically opened. Keep passwords, API keys and sensitive personal information out of notes.

If saving reports a temporary failure, keep the editor open and retry the same text. Retrying the same text from this open editor will not add a duplicate if the first request succeeded. Changing the text after an uncertain save can produce a conflict: review the incident before reopening the editor to add another note.

A note never acknowledges, assigns, resolves or pauses an incident, changes severity, notifies teammates or publishes a status update. Private note text stays out of public widgets/status pages, legacy detection responses and the mobile Detections screen. Only the incident detail loads note text; the monitor and incident lists stay compact.

Incident access and history allowances apply to notes too. A removed incident or deleted tenant removes its notes; the workspace audit records the action without copying note text. Adding notes does not extend the incident’s history allowance.

  1. Open an incident and find Recorded timeline. Choose Add internal note to open the note editor.
  2. Write up to 4,000 characters of plain text, then select Add internal note. A green confirmation means the note is safely on record.
  3. Read notes alongside detection, acknowledgment, assignment, severity and recovery events. Each note shows its recorded author and time. Choose Earlier internal notes to load older entries; use Refresh to pick up new notes from teammates.

Keep corrections clear and remove wording safely

Owners and admins with Manage access to the monitor can correct or remove any note, including notes on recovered incidents within visible history. Viewers and read-only support can read notes and their history but cannot change them. Every save rechecks current access.

Corrections are version-checked. If someone changes a note while you are working, close the editor, select Refresh on the incident and review the latest wording before trying again. A removal opened before a correction cannot silently discard the newer text. Retrying an already saved correction or removal does not create duplicate audit entries.

Each note allows up to 100 corrections. After that, add a follow-up note; removal remains available. Note history loads only when opened, 20 versions at a time, keeping the incident view calm.

Removal cannot be undone, and deleted wording is not available from history or old save retries. The original author, correction/removal authors and recorded times remain as a private record. Notes and their wording never publish automatically or trigger notifications, tickets, recovery or changes to monitor settings.

  1. Beside a note, choose the pencil icon (Correct note). Update its plain text and save. The original author and time stay in place; a quiet line records who corrected it and when.
  2. Choose the history icon (View note history) on a changed note to see its original wording and earlier corrections. Use Earlier versions to continue through its history.
  3. To remove a note, choose the trash icon (Remove note), read the confirmation and select Remove note. Its text and all earlier wording are permanently removed; a Note removed entry preserves the author, times and removal record.

Keep a useful guide close at hand

Every plan supports one primary runbook link per incident. Add or update it on either an open or recovered incident within visible history. Viewers and read-only support can open saved links and read the private change timeline but cannot change them.

Labels allow up to 80 characters and URLs up to 2,048. Embedded usernames/passwords and non-web links such as javascript:, file: or data: are rejected. Internal HTTP documentation is allowed. Keep passwords, secret tokens and sensitive query-string details out of URLs.

UptimeOwl stores the link without fetching, checking, embedding or previewing the destination. Opening it sends no incident URL as a referrer. A runbook is guidance for a person, not an automated recovery action, and does not send notifications, create tickets or publish a public update.

Changes are version-checked. If another teammate changes the guide first, close the editor, select Refresh and review the latest link before trying again. An old removal cannot silently discard a newer link. Retrying the same saved choice does not duplicate change events.

The private timeline records who linked, updated or removed the guide and when; choose Earlier runbook changes for more. Earlier URLs and labels are not copied into this history or the workspace audit. The current link remains private to incident details and does not appear in public status pages, widgets, mobile Detections or monitor/incident lists.

This slice accepts links only. File attachments are a separate future feature; they do not upload through this editor.

  1. Open an incident and find A guide for the next step. Choose Add runbook, paste a full HTTP or HTTPS guide URL and optionally give it a short label. Select Save runbook.
  2. Open the saved link to read the guide in a new tab. Its destination hostname is shown beneath it. You still need permission to access the documentation at that destination.
  3. Owners/admins with Manage access can choose Change or the trash icon (Remove runbook). Review the removal confirmation before choosing Remove link. The guide itself is not deleted.

A moment to look back

After monitoring records recovery, open the incident from Resolved. Owners and admins with Manage access can choose Start review in A moment to look back. Add a summary, impact, cause or lessons learned, then Save review draft. Every plan supports private reviews within its available incident history.

Save a partially completed draft and return with Edit draft. Read private draft expands the saved wording for teammates who can view this monitor. Reviews stay private, and saving them does not change monitoring, send notifications or publish a public update. See the private incident review guide for limits and editing advice.

A saved review also has a collapsed Follow-up actions checklist. Add a short step, optionally assign an eligible teammate and tick it complete when done. Owners/admins with Manage access can edit, reopen or remove actions. The checklist stays private and does not send notifications.

Once a saved review has a short summary, choose Finalize review and confirm to make its wording read-only. Reopen review and confirm before editing again. Follow-up work can continue while the wording is finalized. The private timeline records finalization and reopening; Earlier review changes loads older entries. Nothing is published or sent.

Keep private work separate from public updates

Owners, admins and viewers see only incidents for monitors they can currently view. History allowances still apply to resolved incidents. Open incidents remain available even when their start is outside the ordinary history window. Changed access, retention or deletion can make an older detail link unavailable.

Business and Enterprise owners/admins with Manage access see Public communication on incident details. If your status page is not set up or the monitor is not a currently published component, use the Status page link to prepare it first. Read-only support and viewers do not get these controls.

Choose Draft public update to prepare a private draft with neutral wording. If an update is already linked, Review public draft opens that same update. The section shows its saved public state, whether it has been published and whether saved changes are still unpublished. View public update appears only while both the update and its status page are published.

The public-draft editor offers Open private incident when you can still view the source record within your history allowance. The link may disappear after access changes, retention or deletion; this does not delete an existing public update.

Review public wording and save the draft, then explicitly Publish update and confirm from Status page → Incidents. Saving, acknowledgment, assignment, severity, private notes, runbooks and automatic monitor recovery never publish or resolve a public update. Publish a reviewed Back on watch update separately after recovery.

A HELPING WING

Let’s find your next step.

Open the chat in the corner to ask a question. Prefer email? Drop us a note and we’ll help you from there.

[email protected]