hashicorp
vault secrets operator log on GCP showing up as error
All logs for VSO are showing up as ERROR category logs, please see picture below, is that intended?
if all logs from vso are classified as ERROR level it will trigger people using it think that the current behavior(which is a default behavior is having issues, where as they are just normal operation logs) people will have no incentive to dig through the logs when something actually is wrong with VSO since everything is categorized as a ERROR. When people have setups such as run playbooks when a pod has high error rate, it will cause disruption of other application troubleshooting flow since VSO logging is an outlier.
Expected behavior the logging for VSO should be categorized with different log levels. Environment GKE
@nia-potato VSO will only log at the error level when it encounters an error. Are you experiencing something else?
Thanks,
Ben
@benashz as you can see from the screenshot, even debug events or just normal secret sync operations that succeeded are showing up as error level in gcp pod logs. That messes up with our alerting, since we have a few alert logic for pods that is the following condition:
if error level > X amount at X time
Let the project owner know.
Hello, is there any new on this topics ? I can confirm the behaviour as well, all VSO logs are showing as error log on our GCP Log explorer:
