Error logging is broken, or unintuitive

[nijikokun]

I have been trying to re-create the same result as doing a throw err for the past thirty minutes with zero results. I've read the code, it looks as though should the meta object contain the exception (error object) it will return the same stack. Wrong. It does not.

The top, is the global.log.error(err), the bottom is the throw err, wow, look at how much more information is displayed, not to mention you even get the error and stack from the throw err:

Here is the (full) code:

mongoose.connection.on('error', function (err) {
  global.log.error(err)
  throw err
})

I have also tried:

global.log.log('error', { meta: err })

At least using that I get... the error message, that's it.

How do you log new Error objects properly? It is a mystery at this point, throwing them seems to be my best option, and that makes me feel extremely dirty.

[alexandrubau]

I think that Error is not being detected as metadata. I've also noticed this behaviour with big objects, not only Error.

[alexandrubau]

I think it's related to #280. Should be reopened.

[nijikokun]

Yes, as it was not fixed @indexzero please comment, as this is critical 🔥

[indexzero]

This is not related to #280. It's something else which happens to have the same symptom.

[nijikokun]

is there any update @indexzero ?

[alexandrubau]

@nijikokun I hope they merge #777. Seems to be a fix.

[indexzero]

Duplicate of #745. Locking this issue as a point of process for duplicate issues.