Repository navigation
Add opt-in Prometheus outbox queue lag metrics - #270
Merged
Merged
Conversation
Benchmark gate✅ gate passed
Gated (fails the build): |
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
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.
Summary
PrometheusRecorder(queue_lag_interval_seconds=60). Sampling is disabled by default and follows the broker lifecycle.Benchmark
Postgres 17, one million rows per queue, 25 samples per case. Median / p95 query round-trip times in milliseconds.
EXPLAIN ANALYZEshowed scans over all active leases with the existing indexes in the lease-heavy cases. The optional index allowed an index-only scan bounded by the expiry cutoff. The benchmark used a static backlog, so it does not measure index maintenance cost under concurrent writes.Verification
830 tests passed against Postgres. Ruff, type checking, and the strict docs build passed.