# Transaction Name | Sentry for Zap

The current transaction name is used to group transactions in our [Insights](https://docs.sentry.io/product/insights.md) 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:

* `GET /api/{version}/users/`
* `UserListView`
* `myapp.tasks.renew_all_subscriptions`

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.

To override the name of the currently running transaction:

```go
transaction := sentry.TransactionFromContext(ctx)
if transaction != nil {
	transaction.Name = "UserListView"
}
```

Please refer to [the tracing documentation](https://docs.sentry.io/platforms/go/guides/zap/tracing.md) for how to start and stop transactions.
