Incident Schema for Manual Incident Creation
Use this guide when your team wants to start incidents manually from the Incidents page.
Manual incidents in 1stLine by Burava begin from an enabled Alert Schema selected as the incident schema.
You can create Alert Schemas that are reserved only for manual incident start. Each reserved schema acts like an incident template for a different use case.
What you need
- access to Create Alert Schema
- permission to create or edit Alert Schemas
- a library schema intended for incidents
Steps
- Open Create Alert Schema.
- On Choose Schema Source, choose Choose from Library.
- Open Select Library Schema.
- Choose a library schema intended for incidents.
- Click Select.
- Review the created schema.
- Make sure the schema is enabled.
- Confirm the schema fits the manual incident workflow your team wants to use.
- Repeat this process for each manual incident template your team needs.
For manual incidents, the app can use incident schema defaults for:
titleprioritydescriptionlabels
That means a good incident schema can make manual incident creation faster and more consistent.
When a user starts a manual incident from this schema, 1stLine creates an Alert Instance through the schema and links the Incident to that generated Alert Instance. The schema sample and patterns define the alert-shaped payload that represents the manual incident.
By creating multiple reserved incident schemas, you can offer different manual incident templates. For example:
- production outage
- security incident
- customer escalation
- data pipeline incident
Each template can have its own default payload shape, priority, description, labels, lifecycle mapping, and receiver behavior.
Before you start using it
Review the full workflow around the incident schema:
- Routing Rules
- Chains
- Lines
- Line Members
- Communication Rules
- Incident Actions if you want lifecycle notes or webhooks
This matters because the incident schema is part of the full response path, not just a form default.