Skip to content

binary replication montitoring metrics #1

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

Closed
jinty opened this issue Dec 14, 2015 · 3 comments · Fixed by #11
Closed

binary replication montitoring metrics #1

jinty opened this issue Dec 14, 2015 · 3 comments · Fixed by #11

Comments

@jinty
Copy link
Contributor

jinty commented Dec 14, 2015

Hi,

I'm interested in using your exporter to monitor a streaming replication cluster. However it looks like it's missing a few metrics, specifically these would be interesting:

pg_is_in_recovery()
pg_last_xact_replay_timestamp()
pg_last_xlog_replay_location()
pg_last_xlog_receive_location()
pg_current_xlog_location()
pg_is_in_backup()

from http://www.postgresql.org/docs/9.4/static/functions-admin.html

@jinty
Copy link
Contributor Author

jinty commented Dec 14, 2015

sorry for not attempting a pull request, but, er never done any go programming before and whatever I did would probably need a re-write...

@wrouesnel
Copy link
Contributor

No problem - I am interested in supporting those in metrics. I'll have
to examine our current postgres instance, since I believe our DBAs set
up replication so I should have a good test case.

On 15/12/15 03:59, Brian Sutherland wrote:

sorry for not attempting a pull request, but, er never done any go
programming before and whatever I did would probably need a re-write...


Reply to this email directly or view it on GitHub
#1 (comment).

@wrouesnel
Copy link
Contributor

We have pg_stat_replication now, but looking at this list again it's not actually what you were looking for. The new code to handle it extends the model quite well though, so we should be able to support this. Leaving this open after all.

gsstark pushed a commit to gsstark/postgres_exporter that referenced this issue Oct 1, 2020
…es a query timeout. If it takes longer than that to run a query, exit with error. This is a stopgap effort to fix prometheus-community#1 until the real issue is fixed upstream in gofreetds.
Sticksman pushed a commit to Sticksman/postgres_exporter that referenced this issue Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants