Back to use cases
IT
Support & incidents
The IT department handles incidents and support. Origin 137 aggregates signals (SIEM, APM, logs), runs playbooks and produces evidence for post-mortems.
Problem
Alerts and requests are scattered (email, tickets, Slack), playbooks are manual and evidence for post-mortems is hard to assemble.
Impact
Lower MTTR, consistent playbook execution and evidence production for incident reviews.
Solution
- Aggregate signals (SIEM, APM, logs) into a unified timestamped context.
- Select and run the right playbook by incident type.
- Use AI to summarise logs and suggest remediation actions.
- Generate an evidence pack (timeline, actions, approvals) for audit.
Control points
- •Separation of execution and approval
- •Timestamped immutable evidence
- •Mandatory review before destructive actions
Indicators
- •MTTA / MTTR
- •Playbook execution without deviation
- •Time to produce post-mortem
Concrete examples
- •Prod incident: log aggregation, restore playbook, post-mortem
- •Access request: manager approval, AD update, notification
- •Patching: schedule, validation, rollback on error
Typical tools
PagerDutyJiraSlackGrafanaDatadog
Ready to get started?
Book a slot for a demo tailored to your function.