@sentry/nextjs not reporting issues i serverless functions

[ThePaulMcBride]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

6.5.1

Description

I've recently started using the @sentry/nextjs package for a Nextjs site. I've followed through with the installation guide with one exception. I'm using environment variables instead of the file generated by the wizard. On the client side it works great, the releases and bugs are being tracked, but I'm getting no reports from my serveless functions when they throw errors.

import { withSentry } from "@sentry/nextjs";

const handler = async (req, res) => {
  throw new Error("API throw error test");
  res.status(200).json({ name: "John Doe" });
};

export default withSentry(handler);

This is the serverless function I am testing and nothing is showing up in my Sentry dashboard when it fails.

[AbhiPrasad]

Hey, thank you for reporting. Could you share your next config with us? Also, is this happening during local development, or when deployed on something like Vercel?

[ThePaulMcBride]

Sure, The contents on my next.config.js is below...

const { withSentryConfig } = require("@sentry/nextjs");
const withImages = require("next-images");
const withBundleAnalyzer = require("@next/bundle-analyzer")({
  enabled: process.env.ANALYZE === "true",
});
const webpack = require("webpack");
const withPlugins = require("next-compose-plugins");
const withTM = require("next-transpile-modules")(["@medv/finder"]);

const basePath = "";

const nextConfig = {
  basePath,
  productionBrowserSourceMaps: true,
  images: {
    domains: ["x", "y", "z"],
  },
  webpack(config, options) {
    config.module.rules.push({
      test: /\.ejs$/,
      use: {
        loader: "ejs-compiled-loader",
        options: {
          htmlmin: true,
          htmlminOptions: {
            removeComments: true,
          },
        },
      },
    });

    config.module.rules.push({
      test: /\.worker\.js$/,
      use: { loader: "worker-loader" },
    });

    config.plugins.push(
      new webpack.ProvidePlugin({
        _: "underscore",
      })
    );

    config.plugins.push(
      new options.webpack.DefinePlugin({
        "process.env.NEXT_IS_SERVER": JSON.stringify(
          options.isServer.toString()
        ),
      })
    );

    return config;
  },

  async redirects() {
    return [
      {
        source: "/",
        destination: `${process.env.API_URL}/`,
        permanent: true,
      },
      {
        source: "/blog",
        destination: `${process.env.API_URL}/blog`,
        permanent: true,
      },
      {
        source: "/blog/:slug*",
        destination: `${process.env.API_URL}/blog/:slug*`,
        permanent: true,
      },
      {
        source: "/changelog",
        destination: "/changelog/page/1",
        permanent: true,
      },
    ];
  }
};

const SentryWebpackPluginOptions = {};

// Make sure adding Sentry options is the last code to run before exporting, to
// ensure that your source maps include changes from all other Webpack plugins
module.exports = withPlugins(
  [
    withBundleAnalyzer,
    withImages,
    withTM,
    [withSentryConfig, SentryWebpackPluginOptions],
  ],
  nextConfig
);

This happens when deployed to vercel, though it doesn't report errors locally either (is it supposed to?).

[a-ayala]

same issue here, any luck?

[ThePaulMcBride]

No, I've not managed to get it working yet

[nickfreeman]

6.5.0 originally broke all serverless functions. 6.5.1 definitely broke reporting. Any serverless function wrapped with withSentry that throws an error will not trigger a Sentry error in production. Reverting back to 6.4.1 has fixed this

[DavidChouinard]

For context: we had this issue when we first manually integrated Sentry with Vercel (before the Next.js plugin). The issue, as I remember, is that Sentry queues up exceptions to be sent to the server but Vercel terminates the function instantaneously — causing the exception to be lost.

Adding await Sentry.flush(2000) to the error path fixed the issue, the Next.js library should probably do that by default.

[nickfreeman]

@DavidChouinard interesting, having no issues with error logging for serverless Vercel functions in 6.4.1 but also tried 6.7.2 yesterday which was unable to log exceptions for serverless functions

[Vadorequest]

For me, all serverless endpoints are broken when wrapping them with withSentry. See #3750

Reverting to 6.4.1 didn't change anything.

[ThePaulMcBride]

Yeah I have this running on a few projects hosted on Vercel and the server side error are never reported

[Vadorequest]

@ThePaulMcBride Maybe this comment might give you some direction. #3691 (comment)

I only fixed this issue myself yesterday, it's under-documented, unfortunately.