8000 Stack traces are lost when log events are seralized · Issue #671 · log4js-node/log4js-node · GitHub
[go: up one dir, main page]

Skip to content
Stack traces are lost when log events are seralized #671
Closed
@itaysabato

Description

@itaysabato

When using a cluster, if I get an error that has own properties, its stack trace is not logged.

Example:

const err = Error();
err["I am"] = "all alone";

logger.error(err);
// produces: "{ 'I am': 'all alone' }"

Looking at the code, it's clearly because of this condition.

There should be a way to serialize additional props along with the stack and message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0