Skip to content

Commit 253c34e

Browse files
committed
feat: add deprecation warning for metrics
1 parent 09ceaf5 commit 253c34e

File tree

1 file changed

+12
-4
lines changed
  • content/200-orm/200-prisma-client/600-observability-and-logging

1 file changed

+12
-4
lines changed

content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,25 @@ sidebar_class_name: preview-badge
66
toc_max_heading_level: 4
77
---
88

9-
<TopBlock>
109

1110
Prisma Client metrics give you a detailed insight into how Prisma Client interacts with your database. You can use this insight to help diagnose performance issues with your application.
1211

13-
<Admonition type="info">
12+
:::info
1413

1514
If you want an even more detailed insight into your Prisma Client's performance, at the level of individual operations, see [Tracing](/orm/prisma-client/observability-and-logging/opentelemetry-tracing).
1615

17-
</Admonition>
16+
:::
17+
18+
:::warning[`metrics` preview feature is deprecated]
19+
20+
The `metrics` preview feature has been **deprecated** as of [Prisma ORM v6.14.0](https://github.com/prisma/prisma/releases/tag/6.14.0) and will be removed in Prisma ORM v7.
21+
22+
Metrics were originally introduced to provide insights into query and connection behavior. With the changes in the new [query compiler architecture](/orm/prisma-client/setup-and-configuration/no-rust-engine), these values no longer reflect the system reliably. Because of this, we are not continuing support for this feature.
23+
24+
If you need visibility into query or connection pool behavior, we recommend using the *native metrics provided by your database driver* (for example, pool statistics) or setting up *OpenTelemetry* for a more complete observability solution.
25+
26+
:::
1827

19-
</TopBlock>
2028

2129
## About metrics
2230

0 commit comments

Comments
 (0)