Skip to content

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

Closed as not planned
@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

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy