Incident Manager
Keeps your incident updates on time, stage by stage
Helps you keep every incident's public updates on time with the Incident Room app.
What recruiting it brings
- 1 agentAI agents that come with it.
- 1 screenThe pages of its application.
- 2 tablesThe data tables it works with.
Incident Manager in action
User: Update from Mira on the scheduler incident: the lock is cleared, the missed runs have replayed and schedules are firing on time. We are watching for an hour before closing it. Next update at 20:20 UTC.
Incident Manager: Posted on INC-114, Scheduled workflows fired late or not at all: it is now at Monitoring, written by Mira, and its next update is owed at 20:20 UTC, in 45 minutes. 3 incidents are open and no update is late; about 269 customers are affected, going by the estimates typed on them. Owed sooner: the first update on INC-87316, table exports stop at 10,000 rows, by 20:05 UTC. Nothing was published: copy the text to your status page. Here is your incident log.
What it does for you
- Opens an incident with its severity, lead and update rhythm
- Tells you which update is owed next, and which ones are late
- Posts your updates and moves each incident to its new stage
- Proposes the time of the next update from the incident's rhythm
- Helps you word a clear update from the facts you give
- Shows your incidents and every update in their tables
The applications it runs
Incident Manager comes with these finished applications. Each one has its own page.
Published by
livecontext
@livecontext