A downstream reader stopped or is falling behind
Varqeni owns the pipeline into Kafka. The readers of that data downstream belong to you, so a reader problem is reported as a risk, never as a cause.
AvailabilityAvailable to everyone with early access to Varqeni.
Steps
- The status turns amber with Reader stopped or Reader falling behind.
- The headline says Data reaches Kafka. A reader downstream needs a person.
- The Kafka part of the diagram names the reader and what is wrong.
- A notice goes to your Teams channel once, and once more when the reader catches up. No investigation opens and nobody is paged.
What you should see: Stopped means a reader group has no running members while records wait for it. Falling behind means it is at least 10,000 records behind and the gap is still growing. Your administrator can change that threshold per pipeline.
What it can and cannot do
Can
- Spot a reader of your change data that stopped or keeps falling behind, and tell Teams once.
Cannot
- Restart or fix a reader, open an incident for it, or page anyone about it.
If it does not work
- Check the reader yourself: is its service running, and is it consuming? Varqeni will not restart it.
Related articles
- Kafka consumer groupsVarqeni reads who consumes your change data downstream, and flags a reader that stopped or keeps falling behind.
- Notices in Microsoft TeamsVarqeni posts a card to a Teams channel when it opens an incident, when the autopilot acts, and when a downstream reader needs a person.
- 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.
Still stuck? Contact support or email info@fortisdatagroup.com.