Repository navigation
feat(metrics): commit-time lag gauges for ack and source - #256
Open
iskakaushik wants to merge 1 commit into
Open
iskakaushik wants to merge 1 commit into
iskakaushik wants to merge 1 commit into
Conversation
iskakaushik
force-pushed
the
kaushik/ack-commit-lag
branch
from
October 20, 2026 14:23
3d07545 to
05e2f1c
Compare
iskakaushik
marked this pull request as ready for review
October 20, 2026 15:50
8 tasks
serprex
force-pushed
the
kaushik/ack-commit-lag
branch
3 times, most recently
from
October 23, 2026 20:51
6d6a195 to
dc5def9
Compare
serprex
previously approved these changes
Oct 23, 2026
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
2 times, most recently
from
November 10, 2026 19:30
73f5d25 to
76f7d8e
Compare
harshil-goel
changed the base branch from
main
to
kaushik/bridge-latency-histograms
November 10, 2026 19:38
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 10, 2026 20:22
76f7d8e to
bd042fa
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 10, 2026 21:31
bd042fa to
2980dbe
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 07:26
2980dbe to
3613af5
Compare
serprex
approved these changes
Nov 11, 2026
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 07:48
3613af5 to
acf83fc
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 08:58
acf83fc to
4f38f0c
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 09:32
4f38f0c to
1543b42
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 09:45
1543b42 to
e58bfef
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 11, 2026 11:38
e58bfef to
60431e8
Compare
serprex
approved these changes
Nov 11, 2026
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 17, 2026 10:08
60431e8 to
fb9738a
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 18, 2026 05:11
fb9738a to
1155026
Compare
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 18, 2026 08:12
1155026 to
232cd0e
Compare
Carry the commit record's xact_time with the emitter ack frontier and export it as walshadow_emitter_ack_commit_timestamp_seconds, plus the newest drained commit as walshadow_source_last_commit_timestamp_seconds. Both are Unix seconds, NaN until the first commit, so replication lag is a plain subtraction with no PromQL rate window.
harshil-goel
force-pushed
the
kaushik/ack-commit-lag
branch
from
November 18, 2026 08:44
232cd0e to
c39e676
Compare
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.
What
Replication lag in seconds, with no rate window.
walshadow_commit_timestamp_seconds{at}sourceackUnix seconds. A member is absent until its first commit.
Commits replayed from the backup window or an object-store gap carry their commit time too, so the
ackmember moves through a long replay.PromQL
Tests
commit_ts_advances_with_the_contiguous_frontiercommit_ts_keeps_the_newest_and_ignores_trailingpartial_slices_and_untimed_seqs_do_not_move_commit_tsrender_omits_commit_timestamps_until_the_first