[Bug]: logging "err:" without any context

[MarcusHSmith]

🔎 Search Terms

error logging

The problem

export const ddLogger = createLogger({
  level: 'info',
  exitOnError: false,
  format: format.json(),
  transports: [new transports.Http(httpTransportOptions)],
})

we utilize ddLogger.info and ddLogger.error.

We transport to our Datadog instance.

In Datadog we're receiving tons of logs that are just "err:".

Where could they be coming from?

What version of Winston presents the issue?

3.9.0

What version of Node are you using?

v16.18.1

If this worked in a previous version of Winston, which was it?

No response

Minimum Working Example

No response

Additional information

No response

[paul-uz]

I am seeing this as well in the latest version. I have a console.error in a catch block, and the logs show an error log, with no content

[paul-uz]

Hmm, seems you can't just pass an error object to the error log method, it has to be a string :(

[paul-uz]

Any updates on this? I need JSON format because the simple format doesn't output objects properly.

[DABH]

If it’s an issue that the error object has to be a string, maybe make a pr that allows it to be an Error or a string? That would probably be easy and backward compatible and not hurt performance materially

[paul-uz]

I really wish I had time to contribute to libraries like this. I should probably try and make the effort seeing how much I complain about things but sadly I'm too busy with programming for work that contributing simply isn't cost/time effective currently.

Being brutally honest, something like this, I expect to work out of the box.

JSON formatting shoukd be able to handle error objects.

[whargrave-bjss]

@paul-uz I am testing this now but am able to get an error message with a Json response. What block of code are you using to get this issue?