OpenStatus integration. Triage monitor failures and post updates to your OpenStatus status page.

Praxen Inc. triages every OpenStatus monitor failure, reads response logs and latency to find the cause, and can post updates to your status page when you ask.

Get started for free

What Praxen Inc. does with OpenStatus.

Failures triaged on arrival

Every OpenStatus monitor failure, degradation, and recovery lands in Praxen Inc. as an alert, and an agent triages it the moment it does, correlated with recent changes across the graph.

Uptime mid-investigation

Agents check monitor status, uptime, latency percentiles, and per-check response logs while they work an issue, and every finding is cited back to the monitor behind it.

Status pages as issue comms

Agents publish status reports, post progress updates, and resolve them on your status page; notifying subscribers stays off unless you explicitly ask for it.

First-class in the graph

Monitors and status pages join the context graph as resources, so a failing monitor lands next to the deploy and the services behind it.

How to set up OpenStatus

Open OpenStatus Settings → API Token and create a workspace key.
Use a key with write access, which is required for notification-channel provisioning and status-management tools.
Paste it into Praxen Inc., validate against the workspace and connect.

Permissions and access

OpenStatus connects with a workspace API key with write access. Agents can read monitors and response logs, and can manage monitors, status reports and maintenance windows. The integration provisions a webhook notification channel named praxen; this is not a read-only credential flow.

Discovery, refresh and the connected view

Failure, degradation and recovery notifications reach Praxen Inc. through that channel. Monitors are attached on the channel side, with new monitors added on the next reconciliation pass. Manually detaching a monitor is respected; re-attach it in OpenStatus if its alerts should return. Investigation reads include uptime, latency percentiles, per-check response logs, status page components and overall public status.

Example workflow

Investigate elevated response latency in a monitor’s individual check logs, then use its status page context to prepare a status report. Notifying status-page subscribers is off unless explicitly requested. Maintenance windows can distinguish a planned outage from a newly failing service.

Disconnect and revoke access

Disconnect OpenStatus in Praxen Inc. and revoke the key in OpenStatus. Terraform-managed monitors need no extra recipient field because channel membership is managed on the channel side.

OpenStatus tools.

The calls Praxen Inc. can make to OpenStatus when it looks into an issue.

OpenStatus

openstatusApi Call any OpenStatus API endpoint that lacks a dedicated tool
openstatusMonitors Read, create, update, or trigger OpenStatus uptime monitors
openstatusResponseLogs Read OpenStatus per-check HTTP response logs
openstatusStatusPages Read OpenStatus status pages, their components, and their public status
openstatusStatusReports Read and publish OpenStatus status reports (public incident communication)
openstatusMaintenances Read or schedule OpenStatus maintenance windows

Common questions.

Why does OpenStatus need write access?

The integration creates a notification channel, and agent tools support monitor management, status reports and maintenance windows.

Will a manually detached OpenStatus monitor be reattached?

Manual detachment is respected. Re-attach the monitor in OpenStatus when you want its alerts to reach Praxen Inc. again.

Connect it once. Then get back to shipping.

Get started for free