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.
This pull request adds the
litefs_lag_seconds
gauge and returns the lag behind the primary in seconds. This metrics is server-wide as opposed to the per-dblitefs_db_latency_seconds
metric.It also accounts for heartbeats so replicas that don't receive transactions for more than a second will still have their lag updated. When no transactions are received, a lag of ~1s is normal as that is the heartbeat interval.
The
litefs_db_latency_seconds
metric has been renamed tolitefs_db_lag_seconds
for consistency as well.