What Varqeni reads, and what it does not
Varqeni needs to know how your pipeline is running, not what your data says.
AvailabilityApplies to every Varqeni early access customer and to varqeni.com.
How it works
- It reads states and measures: slot and write-ahead log sizes, heartbeat age, connector and task states and errors, pod states and events, consumer lag, and infrastructure metrics.
- It does not read the contents of your tables or of your change events.
- Error messages and log lines from the pipeline's own components can appear in the evidence, because they explain a fault.
What it can and cannot do
Can
- Read how your pipeline is running: states, sizes, errors and lag.
Cannot
- Read the rows in your tables or the contents of your change events.
Related articles
- How evidence is sealed and keptEach investigation is sealed with a hash chain and stored write-once for one year.
- Read-only identities and the separate executorThe watching agent can only read. Fixes run under a different identity it cannot use.
- How Varqeni is set up on your systemsFortis installs the agent during early access. It reads your pipeline through identities that can only read.
Still stuck? Contact support or email info@fortisdatagroup.com.