You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using express routers a middlewares, sentry create a transaction name including only the path in the last router.
Here is an example:
constexpress=require('express');constSentry=require('@sentry/node');constapp=express();Sentry.init({dsn: 'secret'});constsubRouter=express.Router();subRouter.get('throw-new-error',(req,res)=>{thrownewError('An 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!');});
So here, when I GET /sub/throw-new-error, the transaction name will be GET|/throw-new-error instead of GET|/sub/throw-new-error.
The text was updated successfully, but these errors were encountered:
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
Using express routers a middlewares, sentry create a transaction name including only the path in the last router.
Here is an example:
So here, when I GET
/sub/throw-new-error
, the transaction name will beGET|/throw-new-error
instead ofGET|/sub/throw-new-error
.The text was updated successfully, but these errors were encountered: