add transactionNamingScheme option to RequestData integration

Author: lobsterkatie

packages/node/src/index.ts

@@ -18,6 +18,7 @@ export type {
 } from '@sentry/types';
 export type { AddRequestDataToEventOptions } from '@sentry/utils';
 
+export type { TransactionNamingScheme } from './requestdata';
 export type { NodeOptions } from './types';
 
 export {

packages/node/src/integrations/requestdata.ts

@@ -3,7 +3,12 @@
 
 import { EventProcessor, Hub, Integration } from '@sentry/types';
 
-import { addRequestDataToEvent, AddRequestDataToEventOptions, DEFAULT_USER_INCLUDES } from '../requestdata';
+import {
+  addRequestDataToEvent,
+  AddRequestDataToEventOptions,
+  DEFAULT_USER_INCLUDES,
+  TransactionNamingScheme,
+} from '../requestdata';
 
 type RequestDataOptions = {
   /**
@@ -19,6 +24,9 @@ type RequestDataOptions = {
     user?: boolean | Array<typeof DEFAULT_USER_INCLUDES[number]>;
   };
 
+  /** Whether to identify transactions by parameterized path, parameterized path with method, or handler name */
+  transactionNamingScheme?: TransactionNamingScheme;
+
   /**
    * Function for adding request data to event. Defaults to `addRequestDataToEvent` from `@sentry/node` for now, but
    * left injectable so this integration can be moved to `@sentry/core` and used in browser-based SDKs in the future.
@@ -39,6 +47,7 @@ const DEFAULT_OPTIONS = {
     url: true,
     user: DEFAULT_USER_INCLUDES,
   },
+  transactionNamingScheme: 'methodpath',
 };
 
 /** Add data about a request to an event. Primarily for use in Node-based SDKs, but included in `@sentry/integrations`

packages/node/src/requestdata.ts

@@ -25,7 +25,7 @@ export interface AddRequestDataToEventOptions {
   };
 }
 
-type TransactionNamingScheme = 'path' | 'methodPath' | 'handler';
+export type TransactionNamingScheme = 'path' | 'methodPath' | 'handler';
 
 /**
  * Sets parameterized route as transaction name e.g.: `GET /users/:id`