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
Describe the bug
It appears that the log severity for gha-runner-scale-set is not configurable and defaults to "info". This results in our logging system being overwhelmed with excessive, unnecessary information.
I have noticed a logLevel option in the "gha-runner-scale-set-controller" HELM chart, but it seems to only apply to the controller pods, not the runner pods.
To Reproduce
Use default installation method.
Expected behavior
Having the ability to set log-level on runner application during runtime.
Describe the bug
It appears that the log severity for gha-runner-scale-set is not configurable and defaults to "info". This results in our logging system being overwhelmed with excessive, unnecessary information.
I have noticed a logLevel option in the "gha-runner-scale-set-controller" HELM chart, but it seems to only apply to the controller pods, not the runner pods.
To Reproduce
Use default installation method.
Expected behavior
Having the ability to set log-level on runner application during runtime.
Runner Version and Platform
gha-runner-scale-set-controller - 0.10.1
gha-runner-scale-set - 0.10.1
runner image - v2.322.0
What's not working?
No option to eliminate tones of "info" garbage logs.

The text was updated successfully, but these errors were encountered: