Incident investigation.
Evidence before answers.
Epok's evidence engine turns the telemetry it ingests into evidence items with receipts and coverage. Recognize an incident, assess recovery from change and blast radius, and investigate the cause with the same facts. Epok commits a cause only when the evidence supports it; otherwise it says what is missing and what to check next.
Anomaly & new-error detection.
Surface unfamiliar errors, services gone quiet, and spikes, drops, or drift from normal. Detectors produce evidence from Epok's owned ingest: rule packs match supported inputs as they arrive; learned baselines use service history. Analysis groups related observations into incidents.
See what detection covers →Follow the incident across signals.
Inspect related alerts, affected services, recent changes, and the cascade timeline in one investigation. Logs, traces, RUM, and replay join where they share trace context; metrics and infrastructure correlate by service and time window. Follow stable evidence IDs to receipts and check coverage, including what was not seen.
Customer impact needs a customer identifier. Trace-linked replay needs shared trace context. Your team uses the app, Slack and PagerDuty; agents read the same evidence through the MCP agent gateway, with access on request.
Recover from the change and its blast radius.
Assess a reversible action while root-cause analysis continues. Epok starts with the change and its blast radius, then recommends actions from runbooks and built-in playbooks for known failure shapes. Inspect the evidence, undo path and guards, including when a rollback won't recover the service. Missing evidence and uncertainty remain visible.
We recommend; you execute. No autonomous production changes.
A probable cause. Or "I don't know."
Root-cause analysis tests possible explanations against the evidence. A committed cause cites evidence IDs and their supporting receipts. When no cause is supported, Epok abstains, shows the unresolved candidates, and says what to check next. Coverage distinguishes none in retained data from a check that did not run.
COMMITTED
A probable cause with links to the log lines, spans, or metrics behind it. Check the evidence yourself.
ABSTAINED
Insufficient evidence for one cause. Inspect the ranked candidates, what each is missing, and what to check next.
Forecast saturation, exhaustion and capacity trouble.
Epok projects saturation, exhaustion and capacity breaches from resource trajectories, with an ETA and confidence. Forecasts expose their evidence, data window, coverage and uncertainty so your team and agents can inspect a forming failure and assess preventive action.
Inspect the pipeline →