Logger severity setup not compatible with GCP logger

Steps to reproduce

Expected behavior

textPayload="[watermill] 2026/01/27 11:10:38.827004 connection.go:70: \tlevel=INFO msg="Closed AMQP Pub/Sub" "

I would expect to be severity INFO and not ERROR

Actual behavior

GCP marks as ERROR

Possible solution

All logs go to stderr - GCP Cloud Logging may classify all stderr output as ERROR level Use Structured JSON Logging or change to output to Stdout and stderr