Read the status, headline and measures
The top of the Overview answers one question: does anything need a person right now, across everything Varqeni watches? Below it, the same answer for the system you have chosen.
AvailabilityAvailable to everyone with early access to Varqeni.

Steps
- Now, across every system. One quiet line at the top greets you and says what needs a person, or that nothing does, how many systems are healthy and when it was checked. When something needs a person the line turns amber or red, says what, and takes you to it when you choose it. Under it comes the live picture of the area you are in: the pipeline diagram for Data, the estate orbit for Infrastructure, your services for Service. Under that, a card for each operations area counts its healthy systems, For you lists the fixes waiting for your approval, Pulse gives each system one row, grouped by area: its state in a few words and its two or three key signals as lines over the last three hours, and What Varqeni did on its own lists what the autopilot, a runbook or the data check did without a person.
- Choose an area card to switch to that area, or a waiting fix to open its incident, where approving still asks you to confirm.
- In Pulse, point at a line to read its value at any moment, or tab to it and use the arrow keys (Home and End jump to the ends, Esc goes back to now). Choose a system's name to open it, or the map button at the end of its row to see it on the live map.
- Status at the top right. Data flowing (green) means every check passed. 2 signals (red) means two checks failed. Reader stopped or Reader falling behind (amber) means a downstream reader needs a person while your pipeline itself is fine.
- The headline says what Varqeni sees in one sentence. The line under it says what it may do: observe and report, act with a named approval, or act within a written policy.
- Heartbeat age is how many seconds ago the last heartbeat row reached the pipeline. It should stay low and steady.
- WAL held by slot is how much write-ahead log PostgreSQL keeps for the replication slot. It should not keep growing.
- Investigations, 24 h counts investigations opened in the last day.
What you should see: The pulse lines come from your Prometheus, read with fixed queries, so they show the last three hours even right after the console restarts; a signal Prometheus does not keep starts from the console's own readings. The console has one theme, dark, made for long hours on a laptop or a wall screen; printed and saved reports come out black on white.
What it can and cannot do
Can
- Tell you in one line whether data is flowing, and show each system's key signals over the last three hours, readable at any moment.
Cannot
- Show history beyond three hours on the Overview. Investigations and your Prometheus hold the longer history.
If it does not work
- If the status stays at Connecting, see The console is stuck on Connecting.
Related articles
- Read the live pipelineThe Overview opens on your pipeline: the diagram first, then a panel with each part's key number, its recent history and the rate moving between parts.
- When the Varqeni mark pulsesThe dot in the Varqeni mark at the top left pulses only when a person is needed.
- What each cause meansThe causes Varqeni names for a change data capture pipeline, in plain words.
Still stuck? Contact support or email info@fortisdatagroup.com.