adds pointless `projects/{{projectId}}/logs/winston_log` property to logs when `redirectToStdout` is set to `true`

[macrozone]

Environment details

• OS:
• Node.js version: 16.19.1
• npm version:
• @google-cloud/logging-winston version: 5.3.0

Steps to reproduce

1. create the following log:

const googleCloudLogger = new LoggingWinston({
  redirectToStdout: true,
})

2. deploy to cloud run
3. logs will then look like this:

you notice that it adds an additional logName property projects/{{projectId}}/logs/winston_log which adds noise to it and is even the first thing you see and therefore makes it hard to read the logs.

you also see that the real correct logName is also visible one level above

[fairojm]

If we use useMessageField option set to false then logs are appearing fine in cloud run.

[pebo]

If we use useMessageField option set to false then logs are appearing fine in cloud run. Are you using redirectToStdout: true? I get the logName added when using:

redirectToStdout: true,
useMessageField: false,

[cindy-peng]

Hi @macrozone , could you try useMessageField and see if you are still running into this? useMessageField is used to control if "message" field is used to store structured, non-text data inside jsonPayload field when redirectToStdout is set.

[cindy-peng]

Closing issue as setting useMessageField to false will solve the issue here.

[evil-shrike]

I'm having the same issue with useMessageField: false and redirectToStdout: true.

[evil-shrike]

please re-open