hashicorp / hashicorp/vault-secrets-operator
vault secrets operator log on GCP showing up as error
- Dominant language
- Go
- Stars
- 600
- Forks
- 146
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 6
Description
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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the logging behavior in the stated GKE environment and inspect how VSO emits and categorizes its logs. Done means normal-operation messages use appropriate non-error levels while genuine failures remain categorized as errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud, kubernetes
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100