How Varqeni is set up on your systems
You do not install Varqeni on your databases or brokers yourself. During early access, Fortis sets it up with you. This is what that involves.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- A read-only PostgreSQL role that can see the replication slot, write-ahead log, publication and heartbeat. It cannot change data.
- Read access to Kafka Connect, through a read-only proxy or the Strimzi resources, for connector and task state.
- Read access to Kubernetes for the pods, events and worker logs behind the pipeline.
- Prometheus, if you run it, for Kafka consumer groups and, for Infrastructure Operations, the metrics it already collects.
- A separate executor identity, only if you choose to allow fixes: for pipelines, a port-forward to Kafka Connect; for hosts, a login that can run only a few fixed commands; for Kubernetes, permission to restart or roll back Deployments in the namespaces you list. The watching agent never holds any of it.
What you should see: Once set up, the console shows your pipeline under its own name, and Systems lists it with its connector and slot.
What it can and cannot do
Can
- Read your pipeline through read-only identities, with no software added to your databases or brokers.
Cannot
- Run sidecars or agents on your databases, or work with managed cloud PostgreSQL yet.
Related articles
- PostgreSQLVarqeni reads your self-managed PostgreSQL through a read-only role: replication slot, write-ahead log, publication and heartbeat.
- What Varqeni reads, and what it does notVarqeni reads the state of your pipeline, never the rows of your data.
- Add or remove peopleSign-ins come from your identity provider. What each person may do is set in Users and access.
Still stuck? Contact support or email info@fortisdatagroup.com.