The current transaction name is used to group transactions in our Performance product, as well as annotate error events with their point of failure.
The transaction name can reference the current web app route, or the current task being executed. For example:
Ideally, the transaction name does not contain variable values such as user IDs but has rather low cardinality while still uniquely identifying a piece of code you care about.
A lot of our framework integrations already set a transaction name, though you can set one yourself.
You'll first need to import the SDK, as usual:
import * as Sentry from "@sentry/node";
To override the name of the currently running transaction:
Please refer to the tracing documentation for how to start and stop transactions.