Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] extract Error.cause stacks when logging errors #168

Open
gioragutt opened this issue Nov 15, 2023 · 1 comment
Open

[Feature Request] extract Error.cause stacks when logging errors #168

gioragutt opened this issue Nov 15, 2023 · 1 comment
Labels
agent-nodejs Make available for APM Agents project planning. community

Comments

@gioragutt
Copy link

Now that Error.cause is somewhat standard, it's be great if the cause chain's stack traces would also be extracted when logging errors, sort of like the default .toString() of exceptions in Java.

From what I could gather in the code, only err.stack is extracted.

Looking at recent NodeJS docs, it does look like the internal formatter/inspector already handles the cause of an error when printing it.

@github-actions github-actions bot added agent-nodejs Make available for APM Agents project planning. community triage labels Nov 15, 2023
@trentm trentm removed the triage label Dec 4, 2023
@cosieLq
Copy link

cosieLq commented Jul 24, 2024

This feature would be very handy. What's the progress about it? I'd like to implement it. Maybe integrate the cause into the field stack_trace. Would it be also a useful feature to print out the errors field of AggregateError?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-nodejs Make available for APM Agents project planning. community
Projects
None yet
Development

No branches or pull requests

3 participants