INCIDENTOPS & RUNBOOKS
Incident Management, On-Call and Signed Paging
Give the team a shared response workflow from an observed failure to a reviewed resolution. Spekra records the incident, the responder handoff and the evidence needed for follow-up.
Guided pilot scope · Reviewed 2026-10-16. No production AI diagnosis, automatic infrastructure/DDL remediation or compliance certification is offered.
Keep incident context together
Declare an incident or open one created by a supported monitoring workflow. Track status and timeline events; inspect related traces, logs, query aggregates, host samples or synthetic checks in the shared investigation window.
Explicit identifier links and time/service associations are labelled separately. Narrow truncated windows and verify relevance before deciding a cause.
Plan on-call coverage
Configure standing responders, scheduled shifts, finite daily/weekly rotations and temporary overrides across primary, secondary and tertiary tiers. Timezone-aware handovers and a coverage calendar help expose gaps and overlaps.
Rotations are finite and need renewal. An uncovered scheduled period remains visible as a gap rather than silently assigning an arbitrary responder.
Page and confirm response
Configure a customer-operated public HTTPS receiver. Spekra sends generic JSON; the receiver handles downstream notifications. Opt-in signing authenticates the raw request and supports staged key rotation.
Receiver HTTP acceptance, delivery callbacks and authenticated responder acknowledgement are distinct states. Optional escalation advances through the configured tiers when acknowledgements are overdue. Persisted deadlines survive restart; downtime and load can delay execution.
Review exceptions and verify recovery
Use receiver checks, the attention queue and audited re-paging to review failed, uncertain, blocked or exhausted response paths. Supported production runbooks capture incident evidence and perform configured endpoint verification with retained execution history.
Shell execution, automatic infrastructure changes, built-in telephone/SMS delivery and certified native paging-provider adapters are unavailable. Validate your receiver end to end before operational reliance.
Frequently asked questions
Does a successful webhook mean someone acknowledged?
No. HTTP acceptance means the receiver accepted the request. A signed-in assigned responder acknowledgement or a validated mapped acknowledgement callback establishes a separate response state.
Can the system automatically escalate an unacknowledged page?
An administrator can enable bounded primary-to-secondary-to-tertiary escalation. Acknowledgement, resolution or applicable access/policy changes stop waiting work; a send already in progress cannot be recalled.
Can runbooks execute arbitrary shell commands?
No production shell executor is supported. Production runbooks cover defined evidence capture and endpoint verification actions, with authorization and execution records.
Evaluate your own workflow
Start with supported sample or staging infrastructure and agree on a success measure. Contact the operator to arrange a pilot. This static website does not create accounts or send invitations automatically.
Request a guided pilot →