Hey team!
I'm opening this issue to get a sense of whether Que maintainers are supportive of an attempt to instrument the upstream Que project with native Prometheus metrics. We have an old fork of Que that we've modified to include this instrumentation, but are keen to move back to upstream- before we try porting our metrics, it would be good to understand if the project would be receptive to this attempt!
I've attached a dashboard from a staging environments as an example of some top-level metrics we have. We've also tracked internal processes like job lock acquisition, which has helped us alert on degraded performance (as an example, whenever long snapshots are held open) in the past.
Is this something that would be welcomed by the maintainers?
Cheers,
Lawrence
Hey team!
I'm opening this issue to get a sense of whether Que maintainers are supportive of an attempt to instrument the upstream Que project with native Prometheus metrics. We have an old fork of Que that we've modified to include this instrumentation, but are keen to move back to upstream- before we try porting our metrics, it would be good to understand if the project would be receptive to this attempt!
I've attached a dashboard from a staging environments as an example of some top-level metrics we have. We've also tracked internal processes like job lock acquisition, which has helped us alert on degraded performance (as an example, whenever long snapshots are held open) in the past.
Is this something that would be welcomed by the maintainers?
Cheers,
Lawrence