OpsKnightAlert normalization and payload enrichment.
Extract critical metadata, normalize severity across disparate monitoring providers, and enrich incidents with tier and diagnostic context before paging responders.
Read the operational guideSERVICE AUTOMATION
Alert normalization, routing rules, and automated triage.
Evaluate incoming alerts with deterministic first-match rules, test safely in shadow simulation, and hand off remediation to authorized Runbooks.
WHAT IT SOLVES
First-match rules with response context.
Incoming alerts match ordered service automation rules with deterministic first-match semantics. Decisions capture immutable, checksum-verified normalization context before routing.
Understand the capability01First-match alert routing rules
02Context enrichment and normalization
03Shadow mode rule simulation
OPSKNIGHT / PRODUCT VIEW Northstar Systems · v2.1.0
HOW IT WORKS
A concrete operational path, not a feature list.
AUTOMATION ENGINEFirst-match rule evaluation, payload mapping, and verified auto-recovery.
01Payload context
02Rule evaluation
03Shadow simulation
04Action dispatch
05Verified resolution
EXPLORE A WORKFLOW
- 01Incoming payload
- 02Context extraction
- 03First-match rule
- 04Action dispatch
Evaluate incoming alert payloads against ordered service rules with first-match evaluation and immutable context capture.
OPERATIONAL DEPTH
Service automation, beyond the happy path.
The details below are the parts teams need when evaluating how the capability behaves during real response, failure, and handoff.
Shadow simulation before live activation.
Evaluate new routing and triage rules against live production alert traffic in shadow mode. Inspect aggregate metrics and simulated decisions before activating rules.
Read the operational guideDraft versioning and published immutability.
Draft rules in safety. Publishing requires administrative privilege and creates an immutable, cryptographically hashed rule version with rollback support.
Read the operational guideRemediation handoff to automated runbooks.
When triage requires automated intervention, service rules cleanly hand off to pinned, authorized Runbooks for isolated execution through private agents.
Read the operational guideKNOW BEFORE PRODUCTION
Validate the boundary, not just the happy path.
Use a test service and representative provider configuration before treating service automation as production incident infrastructure.
Service Automation is Beta in OpsKnight v2.1.0. Automatic rules save paused by default; test first-match rules and shadow simulation before enabling automated resolution.
- 01Test first-match rules against payload mappings and verify context capture.
- 02Evaluate rules in shadow mode to observe simulated decisions against live traffic.
- 03Require administrator unattended-write authorization before enabling verified recovery.
DOCUMENTATIONSetup, authorization, limits, and troubleshooting.
Explore service automation documentationYour incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.1.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations