Content-Length: 295304 | pFad | http://github.com/getsentry/sentry-javascript/issues/16740

91 Sentry AWS Node Lambda ESM integration not capturing `console.error` · Issue #16740 · getsentry/sentry-javascript · GitHub
Skip to content

Sentry AWS Node Lambda ESM integration not capturing console.error #16740

Open
@apetta

Description

@apetta

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

I've setup Sentry on an AWS node lambda as per this guide, opting for the NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto" approach.

It works fine when an error is thrown, but does not work for console.error() messages.

I would have expected this to work by default...

Expected Result

Sentry should automatically capture error logs from console by default.

Actual Result

Nothing captured

Product Area

Issues

Link

No response

DSN

No response

Version

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: http://github.com/getsentry/sentry-javascript/issues/16740

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy