Database queries can now be traced to specific services
Identifying the source of heavy database queries should be easier. Developers can now trace database load back to specific services through updated Prisma connection tags.
When a database query spikes in a multi-app architecture, figuring out which service is responsible can be a guessing game.
Developers can now trace database load directly back to the service that generated it. The webapp's database connections are now automatically tagged with the environment's specific service name.
This takes the mystery out of database performance monitoring. When checking database activity logs, teams can immediately see exactly which service is driving the traffic, making debugging and resource optimization faster. This is being rolled out in the webapp database client configuration.
View Original GitHub Description
Sets application_name on the Prisma writer and replica connection strings using the existing SERVICE_NAME env var, so DB load can be attributed by service.