Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added postgresql_replication collector. #323

Closed
wants to merge 4 commits into from

Conversation

DavidValeri
Copy link

New metrics:

  • postgresql.replication.upstream.lag.time - Milliseconds since pg_last_xact_replay_timestamp
  • postgresql.replication.upstream.lag.bytes - The difference, in bytes, between pg_last_xlog_receive_location and pg_last_xlog_receive_location
  • postgresql.replication.downstream.count - The number of walreceivers connected to the DB
  • postgresql.replication.downstream.lag.bytes - The difference, in bytes, between the sent location and the replayed location for each walreceiver
  • postgresql.replication.recovering - The value of pg_is_in_recovery
  • postgresql.replication.walreceiver.running - One if a walreceiver process is running on the machine, otherwise zero.

DavidValeri and others added 2 commits June 6, 2016 09:03
Refactored common Postgresql code into postgresqlutils and improved documentation for where postgresqlconf lives.
postgresql.replication.upstream.lag.time - Milliseconds since pg_last_xact_replay_timestamp
postgresql.replication.upstream.lag.bytes - The difference, in bytes, between pg_last_xlog_receive_location and pg_last_xlog_receive_location
postgresql.replication.downstream.count - The number of walreceivers connected to the DB
postgresql.replication.downstream.lag.bytes - The difference, in bytes, between the sent location and the replayed location for each walreceiver
postgresql.replication.recovering - The value of pg_is_in_recovery
postgresql.replication.walreceiver.running - One if a walreceiver process is running on the machine, otherwise zero.
@johann8384
Copy link
Member

Before your code changes can be included, please file the Contribution License Agreement.

@johann8384 johann8384 modified the milestones: 1.3.2, 1.3.3 Jul 6, 2016
@mathpl
Copy link
Contributor

mathpl commented Apr 19, 2017

Anything we can do to help get this merged? Test failures appear unrelated to the actual code changes.

@vfiset
Copy link

vfiset commented Mar 27, 2018

hi @johann8384 any chance we could merge this PR? looking at the travis logs the collector we added is not the one making the tests fail.

@johann8384
Copy link
Member

Sure, let me look at this today. I don't see why not!

@johann8384
Copy link
Member

Merged in #385

@johann8384 johann8384 closed this Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants