Investigations
How Varqeni finds a cause, and how to read the evidence behind it.
- How an investigation startsVarqeni opens an investigation when a fault holds for two checks in a row, and not again for the same fault.
- Filter the investigations listShow all investigations, only faults, only those the watch service opened, or blind trials.
- Read an investigationOpen an investigation to see the cause of record, the model review, what was ruled out and what a person should do next.
- Causes, citations and stepsWhy Varqeni chose a cause, what it read to get there, and every step on one time axis.
- The Evidence and Report tabsEvidence lists every reading Varqeni took. Report is the full write-up, including the command to approve a fix.
- The audit trail and the verified sealEvery step is written to a hash chain, and the copy you read is checked against the locked one. The seal tells you nothing was altered since.
- The incident timelineEverything that happened in one incident, in order, with who did it: from the first signal to the system being healthy again.
- Run an incident: declare, severity, command, updates and action itemsDeclare an incident Varqeni has not seen, set how bad it is, say who leads it, post where it stands and keep a list of what to do afterwards.
- Post-incident write-ups and follow-upsA blameless write-up drafted from the record, ready for you to check, and a follow-up ticket in Jira in one step.
- The platform underneath a data incidentWhen a pipeline breaks because something it runs on broke, the investigation says so: the node, pod or service underneath, named beside the cause.
- Play an incident's storyStep through one incident from the first signal to the evidence, the cause, the platform underneath, the fix, who approved it, what was sent, whether it worked and whether any data was lost.
- Data volume and schema driftVarqeni tells you when change data stops flowing at its usual volume, or when the source table changes shape, even while the pipeline itself looks healthy.
- Check an incident for lost or duplicated dataAfter a pipeline incident, ask Varqeni whether any rows went missing or arrived twice. It compares the source with the topic, read-only.
- What each cause meansThe causes Varqeni names for a change data capture pipeline, in plain words.
- Confidence: high, medium and lowEach cause comes with a confidence. It decides whether the autopilot may act and how sure you can be.
Still stuck? Contact support or email info@fortisdatagroup.com.