Closed marceldegraaf closed 3 years ago
Update: I've spent the last few hours debugging this, pouring over documentation and trying to add/remove various fields in LoggerJSON
to see if that helps. No luck so far.
I've opened a support ticket at Google Cloud, to check if this is caused by a recent change on their end. Will update this issue as I learn more.
Happens for me as well
Google Cloud Support confirmed this was caused by an error in Google Cloud Logging and Google Kubernetes Engine. It seems to have been fixed in the latest GKE updates.
We're using Elixir/Phoenix and LoggerJSON in our Plug pipelines to format log lines for Google Cloud Logging. These log lines used to be shown with proper labels in the GCL summary line, using fields from
httpRequest
:However, today we noticed these logs are no longer shown that way in GCL, instead showing up as an empty string (
""
) with no labels applied:Expanding one of these log lines still shows the required
httpRequest
fields are present, but GCL seems to take thejsonPayload.message
(which is logged as an empty string inLoggerJSON.Plug
) and for some reason no longer shows thehttpRequest
labels:Things I've tried in a fork of LoggerJSON:
nil
inLoggerJSON.Plug
, to see if that would make GCL disregard thejsonPayload.message
and fall back to the properly formatted log line. This doesn't change anything.message
field from the payload altogether, if it's empty. This makes GCL show the JSON payload as the log line, instead of showing the properly formatted log line.Is anyone else experiencing these issues, and do you have any idea how these log lines should be formatted to get proper formatting back in GCL?