Health messages logged with wrong severity

[steven-supersolid]

Running in GKE and viewing logs in Stackdriver Logging, health message logs are still seen when the log filter level is set to Error. The level inside the message is "info" but severity is "ERROR"

E.g.
2018-08-31 17:16:44.000 BST {"msg":"Health Ping Received","level":"info","source":"*gameservers.SDKServer"}

{
 insertId:  "7i33dlfktfmsv"  
 jsonPayload: {…}  
 labels: {…}  
 logName:  "projects/xxx/logs/agones-gameserver-sidecar"  
 receiveTimestamp:  "2018-08-31T16:16:46.466567315Z"  
 resource: {…}  
 severity:  "ERROR"  
 timestamp:  "2018-08-31T16:16:44Z"  
}

Not sure if this is a bug with Agones or a project configuration issue.

[markmandel]

I actually think all logs in gke come through as Error level (not sure why) - but will double check.

[markmandel]

https://cloud.google.com/kubernetes-engine/docs/how-to/logging#best_practices

"Severities: By default, logs written to the standard output are on the INFO level and logs written to the standard error are on the ERROR level. Structured logs can include a severityfield, which defines the log's severity. glog-formatted logs' severity is set automatically"

I wonder if logrus is misconfigured to output on stderr?

Will investigate!