feat(api): count vCons enqueued to ingress lists via the API#193
Merged
pavanputhra merged 1 commit intoJun 11, 2026
Conversation
Add a conserver.api.count_vcons_enqueued counter, incremented at every API site that pushes work onto an ingress list (vCon create, external ingress, bulk re-ingress, DLQ reprocess), labeled with ingress_list and source. Emitted from the API process rather than the worker loop, so arrivals keep being counted even when workers hang — this enables a stall alert that can distinguish "arriving but not completing" from "idle". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
pavanputhra
deleted the
pavankumar/con-618-add-enqueue-side-vcon-counter-so-the-chain-stall-alert-can
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
conserver.api.count_vcons_enqueuedcounter, incremented at every API site that pushes work onto an ingress list, labeled withingress_listandsource:sourcePOST /vcon(withingress_lists)newPOST /vcon/external-ingressexternalPOST /vcon/ingress(bulk)reingressPOST /dlq/reprocessdlq_reprocessWhy
The existing pipeline counters (
conserver.main_loop.count_vcons_received/count_vcons_processed) are all emitted by the worker loop, so they stop together when workers hang — making it impossible for alerting to distinguish "work is arriving but nothing is completing" (a stall) from "nothing is arriving" (idle). This counter is emitted from the API process, so arrivals keep being counted even when workers are stuck.Tests
Counter coverage for all four endpoints (fires with the right name/value/attributes; skips when nothing is enqueued). Full suite: 653 passed, 16 skipped in the conserver container.
🤖 Generated with Claude Code