Post-incident write-ups and follow-ups
The Write-up tab drafts the post-incident review for you from the evidence, the diagnosis, what people and the autopilot did, and the timeline. You check it and add what the record cannot know.
AvailabilityAvailable to everyone with early access to Varqeni.
Steps
- Open an investigation and choose Write-up.
- Read the draft: a summary, what the evidence showed, what was ruled out, the response, the full timeline and follow-ups to consider.
- Choose Copy or Download to take it into your own document or wiki.
- If you are on the on-call rota, choose File a follow-up in Jira. Varqeni files one issue with the write-up and a link back to the incident, and the page records the issue key.
What you should see: The follow-up's key appears in the message at the bottom of the screen and in the incident's on-call history.
What it can and cannot do
Can
- Draft a blameless write-up from the record and file a follow-up issue in Jira once it is connected.
Cannot
- Know why the fault happened at all, or publish the write-up for you. A person checks it first.
If it does not work
- "Jira is not connected to Varqeni": your administrator adds a Jira account and API token on the Varqeni host.
- The draft says what the record shows. Why the fault happened at all, and what would stop it recurring, is for your team to add.
Related articles
- The incident timelineEverything that happened in one incident, in order, with who did it: from the first signal to the system being healthy again.
- Acknowledge, approve, decline or escalate from the consoleEverything a person on call does from the incident panel: acknowledge a page, approve or decline the fix, page the next person, or resolve it.
- Jira and issue trackersVarqeni files a follow-up issue in Jira with the incident write-up. It runs against the Fortis lab's own Jira; other trackers are planned.
Still stuck? Contact support or email info@fortisdatagroup.com.