Instatus
for LuumenAI
Read status page health, then post incident updates as approved steps
Connect Instatus and Luumen can read your status pages, components, incidents, and maintenance windows while you work in the terminal. Ask what customers currently see, or which components are degraded. When it is time to communicate, Luumen drafts the incident, the update, or the component change and shows it to you before anything goes public.
The Instatus toolbox
15 tools: 7 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ComponentGet the current health and configuration of one component on an Instatus status page.
- ReadGet IncidentGet one Instatus incident with its affected components and update history.
- ReadGet MaintenanceGet one Instatus maintenance with its schedule, affected components, automation settings, and update history.
- ReadList ComponentsList components and their current health for one Instatus status page, including child components where present.
- ReadList IncidentsList incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
- ReadList MaintenancesList scheduled and historical maintenances for an Instatus status page.
- ReadList Status PagesList status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
- WriteAdd Incident UpdatePost a public lifecycle update to an Instatus incident and change affected component states. Approval by default
- WriteAdd Maintenance UpdatePost a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. Approval by default
- WriteCreate ComponentCreate a component on an Instatus status page. Approval by default
- WriteCreate IncidentCreate an incident on an Instatus status page with optional affected component states. Approval by default
- WriteCreate MaintenanceSchedule or start a maintenance on an Instatus status page. Approval by default
- WriteUpdate ComponentChange a component's health or presentation on an Instatus status page. Approval by default
- WriteUpdate IncidentEdit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Approval by default
- WriteUpdate MaintenanceFully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Approval by default
One prompt, start to finish
What a governed Instatus run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add incident update, add maintenance update, create component, create incident, and more — is shown as a plan and requires approval by default, including the 6 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Instatus — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
DynatraceProblems, root-cause detail, and metrics beside the session.
DatadogMonitors, dashboards, and logs pulled into the investigation.
GrafanaRead Grafana health, rings, and dashboard data, then push log records with approval
PrometheusAlerts, metrics, and traces from Prometheus in the session that fixes them.Put Instatus to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.