OpenStatus monitor failures investigated as Polylane issues
Connect OpenStatus with one API key and every monitor failure or degradation reaches Polylane as an issue, with monitors and status pages in the context graph.
What changed
Connect OpenStatus with one API key. Polylane adds a webhook notification channel named
polylane to your workspace and attaches it to every monitor, so each failure, degradation and recovery reaches it. Monitors you create later are attached within the hour.
Failures become issues
A failure or a degradation opens an issue, and further notices from the same monitor go to that issue. A recovery lands on the issue timeline as evidence.
Checks and the context graph
Every 30 minutes, checks watch how many monitors fail or are degraded, whether each monitor still runs, probe latency and average uptime. Monitors and status pages join the context graph, and each monitor is linked to the resource that serves its target hostname.
During an investigation, agents read monitors with their uptime, latency percentiles and response logs, status pages, status reports and maintenance windows. See the OpenStatus integration.
Why it matters
A failing probe says which endpoint broke and from where. Linked to the resource that serves that hostname, it gives the investigation a starting point inside your own stack.
How to use it
- In your
OpenStatus dashboard, open Settings, then API Token, and create a key with write access.
- Paste the key into Polylane. It checks the key against your workspace.
- Polylane creates a notification channel named
polylaneand attaches it to every monitor. If yourOpenStatus plan has no room for another channel, Polylane connects without it and failures do not reach it until you free a slot and reconnect.