Skip to content
1stLine Docs 1stLine Docs

Overview

What is 1stLine by Burava?

1stLine by Burava is an alert management and incident response platform built for teams that do not want their alerting setup to be limited by one fixed integration path.

1stLine is designed to connect almost any Alert Producer and Alert Receiver pair where the producer lets you set a destination URL. It keeps the receiver you already use, adds routing and escalation on top, and gives responders direct alert actions without forcing the whole team into a new alert channel.

1stLine can also add AI-assisted diagnostics to the escalation workflow. With AI Escalation, you run the assistant controller in your own environment, choose the tools and context it may use, and review suggested actions before anything is applied.

How 1stLine achieves this flexibility

In a normal 1stLine setup, 1stLine works between your Alert Producer and Alert Receiver. You configure the producer almost as you normally would, but set its destination to the Alert Producer Destination from an Alert Schema. The final receiver can be passed with forwardTo or configured on the schema.

That means 1stLine can add structure, routing, escalation, and response actions while the alert still lands where your team expects it.

Alert Schemas are the flexibility layer. You can create one from a reusable Library Schema or from a real custom payload. Schema Patterns extract the fields that matter from each producer payload, so those fields can drive Routing Rules, Escalation, system mappings, and other alert behavior.

Schema Transformations define what 1stLine sends to the Alert Receiver. They can keep the payload close to the original, reshape it for the receiver, or add generated action links so responders can acknowledge and resolve alerts directly from the receiver message.

See Alert Schemas for more information about Library Schemas, Schema Patterns, Schema Transformations, and schema mappings.

Routing Rules connect matching Alert Instances to Chains. A Chain is built from Lines, and Lines contain Line Members such as Users, Teams, or Schedules. Along with the absence of responder limit, this lets teams model real response paths instead of a single static owner.

See Routing Rules and Escalation for more information about Conditions, Chains, Lines, Line Members, and Schedules. See Limits for more information about usage limits.

Escalate to AI 1stLine provides a unique option to escalate to AI when configured conditions from your alert payload are met. You own the agent, its model costs, and the environment it runs in. You set the context, MCP tools and CLI executables per matched conditions, click a button, and your own agent will perform diagnostics and one click actions.

See Escalate to AI for more information about how to set up and use this unique feature.

Communication Rules, Communication Routines, and Communication Integrations define how responders are contacted during Escalation, including call and SMS actions where configured. The same alert can follow different communication behavior based on its extracted fields.

See Communication for more information about Communication Rules, Communication Routines, and Communication Integrations.

Each incoming alert is tracked as an Alert Instance, so the team can see what happened, who was contacted, lifecycle metrics, the timeline, and what action was taken. Responders can acknowledge, unacknowledge, resolve, Start incident, Join incident, escalate further, or Escalate to AI from the alert flow.

Not every alert needs to become an Incident. When more coordination is needed, an Incident keeps related Alert Instances, Incident Events, and Incident Actions together, so the response can grow from one alert into a shared incident workflow.

See Alert Instances for the full alert path, and Incidents for more information about incident response.

For automation, use the MCP Server or the generated API reference instead of treating these guides as endpoint reference material.