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

Add metricset for replication to Metricbeat Postgresql module #11234

Open
noahbailey opened this issue Mar 13, 2019 · 8 comments
Open

Add metricset for replication to Metricbeat Postgresql module #11234

noahbailey opened this issue Mar 13, 2019 · 8 comments
Assignees
Labels

Comments

@noahbailey
Copy link

Describe the enhancement:

Add a metricset for monitoring Postgresql replication information from the pg_stat_replication table. There are already modules that use similar tables to extract similar data.

https://www.postgresql.org/docs/9.5/monitoring-stats.html#PG-STAT-REPLICATION-VIEW

Describe a specific use case for the enhancement or feature:

This would be great for displaying and tracking the replication time between servers, time taken in each state, and the overall status of the replica set.

Thanks guys!
-Noah

@mmelyp
Copy link

mmelyp commented Apr 14, 2020

+2

@BuffaloWill
Copy link

+1

This feature would help us understand if we have replication lag and, if so, should be alerted.

I would be interested in workarounds to get this information if anyone has them.

@slithernix
Copy link

me too

@chandransajith
Copy link

+1

@botelastic
Copy link

botelastic bot commented Jul 10, 2022

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jul 10, 2022
@mchirilab
Copy link

+1

@Vladislavgen
Copy link

+1

@lalit-satapathy
Copy link
Contributor

lalit-satapathy commented Aug 3, 2023

@ishleenk17,

Since we have a beats PR on this in advanced stage, there are couple of questions for next steps:

  • What's the overall plan to have this new data stream enabled on beats?
  • Is this new data stream also needed in integration?
  • Should we instead explore generic SQL to provide this new data stream in the integration(when we plan to do so.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet