You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Rundeck with multiple node but only one active at a time through the ExecutionMode settings.
We did setup the rundeck_exporter but as the other nodes are not active the exporter are reaching the rundeck url (active node) to fetch data.
This is leading to a certain amount of queries in our DB.
Would it be possible through a settings to have the "rundeck_exporter" check the status of the execution node and stay idle if the status is disable ?
Let me know if you need more information.
Thanks for your exporter :)
The text was updated successfully, but these errors were encountered:
Hey @Zwordi, I've just pushed a new version (v2.6.4) with a new arg --no_checks_in_passive_mode and RUNDECK_EXPORTER_NO_CHECKS_IN_PASSIVE_MODE=<False|True> so the rundeck_exporter stays idle while Rundeck host is in passive mode.
Hello,
We are using Rundeck with multiple node but only one active at a time through the ExecutionMode settings.
We did setup the rundeck_exporter but as the other nodes are not active the exporter are reaching the rundeck url (active node) to fetch data.
This is leading to a certain amount of queries in our DB.
Would it be possible through a settings to have the "rundeck_exporter" check the status of the execution node and stay idle if the status is disable ?
Let me know if you need more information.
Thanks for your exporter :)
The text was updated successfully, but these errors were encountered: