m2dc0d3r
m2dc0d3r
Found some good samples how to get most common monitoring working like disk,filesystem,memory,cpu https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power%20Systems/page/Roll-Your-Own-Performance-Tool
I did use those C examples to extend this project. https://github.com/dlopes7/aix-prometheus-exporter Question is should we go with independent aix_exporter or maybe we could figure out how to incorporate aix support...
And IBM now has go version go1.13.4 aix/ppc64
It should not be possible to make a election when database is down.
Any news?
Hey @niksajakovljevic Same issue i'm seeing.It is really easy to replicate.Just configure 2 adapters with the same leader-election-pg-advisory-lock-id and point to the same Postgresql database.When you start it up it...
Somehow adpater became leader altho there was database connection issue. Aug 22 14:20:29 xxxxxxxxxxx prometheus-postgresql-adapter: {"caller":"log.go:39","err":"error getting DB connection: dial tcp xxxxxxxx:5432: connect: connection refused","level":"error","msg":"Failed while becoming a leader","ts":"2019-08-22T14:20:29.175Z"} Aug...
Maybe this implementation gives idea how to properly handle database outages etc. https://github.com/Klarrio/pglock
When will this be merged to master?
Are there any forks that continue to improve it?