# Monitoring and alerts Monitoring is the watch-the-result step. nimo keeps watching after the first audit by checking speed on a schedule, watching competitor gaps you choose, checking uptime every few minutes, and telling you when something needs attention. Canonical URL: https://heynimo.com/docs/monitoring Markdown URL: https://heynimo.com/docs/monitoring.md ## AI summary Explains the workflow's watch-the-result step: scheduled performance audits, competitor watches, degradation alerts, incident evidence, Linear issues, verification, uptime checks every five minutes, batched notifications, and quiet hours. ## Key points - Scheduled audits build history and detect regressions. - Competitor watches check chosen public URL pairs weekly. - Incident evidence explains meaningful regressions with scoped evidence, owner, confidence, and Linear issue context when enabled. - Uptime checks run every five minutes. - Notifications are batched and quiet during 10pm to 8am Pacific unless urgent. - Use monitoring to watch whether the first safe fix held up over time. ## Sections ### Scheduled audits - Scheduled audits build the history nimo needs to spot regressions. - Use weekly audits for sites that change occasionally. - Use daily audits for important pages, frequent deployments, paid traffic, checkout, lead capture, or client reporting. - Use manual audits when you make a change and want a before-after check. ### Competitor watches - Competitor watches turn a public comparison into a weekly check. - Run a competitor comparison, choose Watch this gap, then sign in or create an account. - nimo saves the two public URLs and checks the pair weekly. - Weekly summaries tell you whether the competitor pulled ahead, you pulled ahead, the gap is tied, or the check did not have enough data. - When public CrUX history is available, weekly summaries can add one short mobile LCP trend line so you can see whether either side is improving. - Competitor watches store normalized public URLs, domains, status, next run time, last run time, a short latest gap summary, and an optional public CrUX trend summary. - They do not store cookies, request headers, credentials, private pages, or raw Lighthouse blobs. ### Manage competitor watches - Open Watches in the app sidebar to review active and paused competitor watches. - Use Pause when you do not want weekly checks for a pair. - Use Resume to start weekly checks again. - Use Edit to rerun the comparison with the same URLs and decide what to watch next. - Use Delete to stop the watch and remove it from your active list. - Paused and deleted watches do not run new weekly checks. - Delete a watch when the competitor is no longer relevant or when you do not want nimo to keep checking that public URL pair. ### Degradation alerts - nimo compares recent audits with previous results and alerts when metrics move beyond normal noise. - The alert explains what changed and what to check first. - Good prompt: Why did this alert fire, and what changed on the page? ### Incident evidence and Linear issues - When performance incident tracking is enabled, a meaningful regression can become an incident with stored proof. - nimo uses baseline and follow-up evidence to show the affected metric, before-after values, scope, evidence refs, likely owner, confidence, and recommendation context. - Incident evidence can appear on the dashboard, site report, and audit history when enough evidence exists. - It is meant for triage, not for storing raw traces or private request details. - If Linear is configured, you can preview the issue nimo would create for an active incident. - Creating the issue requires an explicit create action, and verification waits for a fresh audit after the task, deploy, or manual check. - Weekly summaries can include unresolved incidents, recoveries, open Linear issues, and changed important-page profiles when reporting is enabled. - Slack and Telegram delivery follows your audit notification preferences. ### Uptime checks - Uptime starts automatically when you add a site. nimo checks every five minutes. - Up means the site responded. - Degraded means the site responded, but slowly. - Down means the site timed out, had DNS trouble, or returned a server error. - A 4xx response counts as reachable because many CDNs and WAFs reject automated requests even when the site is alive. ### Quiet hours - Uptime notifications are batched for 90 seconds so one user does not get a message for every site at once. - During 10pm to 8am Pacific time, non-urgent notifications wait unless an incident has lasted 30 minutes or more. - nimo uses batching and a circuit breaker to avoid false notification storms. ## Related docs - [Quick start](https://heynimo.com/docs) - Start the workflow: find the gap, explain why, fix or hand off, and watch the result. - [Set up a site](https://heynimo.com/docs/setup) - Add your site, choose important pages, pick a schedule, and understand what nimo checks. - [Telegram](https://heynimo.com/docs/telegram) - Connect Telegram and use nimo from chat. - [MCP for agents](https://heynimo.com/docs/mcp) - Use public docs MCP, or connect an authenticated MCP client to nimo. - [Audits](https://heynimo.com/docs/audits) - Find the gap with CrUX field data, Lighthouse lab checks, history, and plain-language results.