Logs in GCP Logs Explorer Displayed as Errors Despite level=info in cronitor

[matimercado]

Hi folks!

We are currently running the latest version of the Cronitor Helm chart (v0.5.0) in our GKE cluster. The deployment was performed as follows:

helm repo add cronitor https://cronitorio.github.io/cronitor-kubernetes/

kubectl create secret generic cronitor-secret -n cronitor --from-literal=CRONITOR_API_KEY=<API_KEY_FROM_ACCOUNT>

helm upgrade --install cronitor cronitor/cronitor-kubernetes --namespace cronitor \
  --set credentials.secretName=cronitor-secret \
  --set credentials.secretKey=CRONITOR_API_KEY \
  --set config.sentryEnabled="false" \
  --set config.defaultEnvironment="production"

Problem

Despite seeing the logs with level=info, they are being classified as ERROR in GCP Log Explorer. This results in incorrect visibility and metrics in our cluster.

Attached screenshots demonstrating the issue:

Expected Behavior

Logs with a level of INFO from Cronitor should be displayed as INFO severity in GCP Logging, ensuring accurate metric tracking.

My assumption is that all logs are being sent to standard error, which causes them to be displayed as such in the logs.

We would appreciate your assistance in resolving this issue.

[aflanagan]

Hi @matimercado,

Thanks for reaching out about this. It looks like this is an issue with the logging library that we chose for this project. I'm surprised this is the first time it's come up!

It looks like this library is also no longer releasing updates, so fixing it looks like it's a matter of swapping out logging libraries. If you'd like to open a PR that does that we'd be happy for assistance testing out a replacement! I'll also bring up with the team to figure out when we could prioritize a release ourselves.

[aflanagan]

I've started a PR here - #45

Go tests pass, but e2e tests are failing.

[matimercado]

Thanks @aflanagan! Noticed that all checks have passed now, great.