Sentry AWS Node Lambda ESM integration not capturing `console.error`

[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

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[apetta]

I'm using Pino for logging, so I've managed to do this as a workaround for now:

import * as Sentry from "@sentry/aws-serverless";
import pino from "pino";
import {
  lambdaRequestTracker,
  pinoLambdaDestination,
  StructuredLogFormatter,
} from "pino-lambda";

const destination = pinoLambdaDestination({
  formatter: new StructuredLogFormatter(),
});

const baseLogger = pino(
  {
    level: process.env.LOG_LEVEL || "info",
  },
  destination,
);

// Create a wrapper that sends error and fatal logs to Sentry
const logger = {
  trace: baseLogger.trace.bind(baseLogger),
  debug: baseLogger.debug.bind(baseLogger),
  info: baseLogger.info.bind(baseLogger),
  warn: baseLogger.warn.bind(baseLogger),
  error: (message: string, ...args: unknown[]) => {
    baseLogger.error(message, ...args);
    // Send to Sentry
    try {
      Sentry.captureMessage(message, {
        level: "error",
        extra: args.length > 0 ? { args } : undefined,
      });
    } catch (sentryError) {
      baseLogger.warn("Failed to send error to Sentry", { sentryError });
    }
  },
  fatal: (message: string, ...args: unknown[]) => {
    baseLogger.fatal(message, ...args);
    // Send to Sentry
    try {
      Sentry.captureException(new Error(message), {
        level: "fatal",
        extra: args.length > 0 ? { args } : undefined,
      });
    } catch (sentryError) {
      baseLogger.warn("Failed to send fatal error to Sentry", { sentryError });
    }
  },
};

const withLoggingRequest = lambdaRequestTracker();

export { logger, withLoggingRequest };

It would be great to have console errors caught by default.

[s1gr1d]

Are you using the captureConsoleIntegration? You would need to enable capturing error as Sentry does not capture console.error by default.

[RulaKhaled]

Sentry.init({
  dsn: '__YOUR_DSN__',
  integrations: [
    // Add this to capture console.error calls as Sentry events
    Sentry.captureConsoleIntegration({ levels: ['error'] })
  ],
  // ... other options
});

Add this to your Sentry call

[mydea]

Closing this because this is working as expected, the captureConsoleIntegration is opt-in to capture console.error as well :)

[apetta]

Thank you both!

I'm using NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto" to auto-initialise, and don't want a custom sentry initialisation.

In my view, I think capturing console.error messages should be the default. It seems to be in Python, I don't see why it would need to differ here.