Briefs · Taipei time (GMT+8)

Cognition launches Devin Oncall, which investigates, mitigates and opens a fix PR as soon as an alert fires

一句重點:Oncall has three parts, covering incoming alerts, incident channels and scheduled reports. When hunting for a cause, it looks beyond code to past incidents, runbooks, deployment history and telemetry (Devin docs).

發生什麼事

@cognition announced Devin Oncall. According to Cognition, some large companies already put thousands of alerts a day through it.

In the official docs, Responders pick up alerts arriving from Slack, Microsoft Teams channels or PagerDuty. What on-call staff gain is less noise: a problem that keeps firing won't turn into a stack of duplicate investigations. With Incidents, a newly opened incident channel starts out with Devin's likely root cause already in it; this suits teams that open one Slack channel per incident and give those channels a fixed name prefix. Reports can be scheduled as a weekly on-call handoff, surfacing similar problems that keep coming back and are worth fixing for good (Devin docs).

There's a short wait before you can start: once at least one telemetry tool is connected, Devin usually needs one to two hours to get to know your systems. Each organization goes through this setup only once (Devin docs).

01Sources

  • @cognition: Cognition's official announcement of Devin Oncall
  • Devin Oncall: official docs; Responders / Incidents / Reports, trigger sources and setup steps