This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
[+] add sent_lag and confirmed_flush_lsn_lag fields to replication metrics
#700
Conversation
This file contains 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
bukem
changed the title
|
Thanks. You need to update according files in the metric folder as well |
|
updated the files in the metric folder |
pashagolub
changed the title
sent_lag and confirmed_flush_lsn_lag fields to replication metrics
|
Do you think we need to update Grafana dashboards with these new fields? Or are they solely used with Prometheus? |
|
@pashagolub not sure if the question is to me or to @kmoppel-cognite . In my opinion, it should be added to the "Replication lag" dashboard. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
pg_stat_replication.sent_lag and pg_replication_slots.confirmed_flush_lsn
sent_lagmeasures the amount of WAL data that is pending replication to a specific standby and helps DBA and operators to identify potential performance bottlenecks and optimize the replication process to minimize lag.The
confirmed_flush_lsnof a replication slot indicates the last LSN that has been successfully written to the WAL on the primary server and subsequently replicated to the associated standby server. It can be used as a reference point to ensure replication consistency.