Skip to content

Sentry no longer uses route parameter names for transactions #2967

Closed
@apmorton

Description

@apmorton

Package + Version

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

Version:

5.25.0

Description

Since #2714 sentry no longer uses req.route.path for transaction names, which causes route paramter values to be logged rather than route parameter names

const express = require('express');
const Sentry = require('@sentry/node');

const app = express();
Sentry.init({ dsn: 'secret' });

const subRouter = express.Router();

subRouter.get('/throw-new-error/:example', (req, res) => {
  throw new Error('An ' + req.params.example + ' error');
});

app.use(Sentry.Handlers.requestHandler());
app.use('/sub', subRouter);
app.use(Sentry.Handlers.errorHandler());

app.listen(3000, function () {
  console.log('Example app listening on port 3000!');
});

wget http://localhost:3000/sub/throw-new-error/my-error-type

Transaction as reported using @sentry/[email protected]: GET|/throw-new-error/:example
Transaction as reported using @sentry/[email protected] (or higher): GET /sub/throw-new-error/my-error-type

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions