prisma
diff --git a/‎content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx‎
Lines changed: 1 addition & 1 deletion b/‎content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx‎
Lines changed: 11 additions & 12 deletions b/‎content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx‎
Lines changed: 11 additions & 12 deletions
diff --git a/‎content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx‎
Lines changed: 13 additions & 260 deletions b/‎content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx‎
Lines changed: 13 additions & 260 deletions
@@ -145,7 +145,7 @@ datasource db {
 
 #### Viewing the connection pool size
 
-The number of connections Prisma Client uses can be viewed using [logging](/orm/prisma-client/observability-and-logging/logging) and [metrics](/orm/prisma-client/observability-and-logging/metrics).
+The number of connections Prisma Client uses can be viewed using [logging](/orm/prisma-client/observability-and-logging/logging) and built-in APIs provided by the driver adapter being used.
 
 Using the `info` [logging level](/orm/reference/prisma-client-reference#log-levels), you can log the number of connections in a connection pool that are opened when Prisma Client is instantiated.
 
 
@@ -34,29 +34,28 @@ const prisma = new PrismaClient().$extends({
 The following example uses the `client` component to add two methods to Prisma Client:
 
 - `$log` outputs a message.
-- `$totalQueries` returns the number of queries executed by the current client instance. It uses the [metrics](/orm/prisma-client/observability-and-logging/metrics) feature to collect this information.
+- `$totalQueries` returns the number of queries executed by the current client instance.
 
 :::info
 
 To use metrics in your project, you must enable the `metrics` feature flag in the `generator` block of your `schema.prisma` file. [Learn more](/orm/prisma-client/observability-and-logging/metrics#2-enable-the-feature-flag-in-the-prisma-schema-file).
 
 :::
 
-```ts
+const total = 0
 const prisma = new PrismaClient().$extends({
   client: {
     $log: (s: string) => console.log(s),
-    async $totalQueries() {
-      const index_prisma_client_queries_total = 0
-      // Prisma.getExtensionContext(this) in the following block
-      // returns the current client instance
-      const metricsCounters = await (
-        await Prisma.getExtensionContext(this).$metrics.json()
-      ).counters
-
-      return metricsCounters[index_prisma_client_queries_total].value
-    },
+    async $totalQueries() { return total; },
   },
+  query: {
+      $allModels: {
+        async $allOperations({ query, args }) {
+          total += 1;
+          return query(args);
+        },
+      },
+    },
 })
 
 async function main() {
 
@@ -9,21 +9,10 @@ toc_max_heading_level: 4
 
 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.
 
-:::info 
 
-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).
+:::danger[`metrics` preview feature has been removed ]
 
-:::
-
-:::warning[`metrics` preview feature is deprecated]
-
-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.  
-
-**The `metrics` preview feature is only available in Prisma ORM versions ≤6.13.x.** If you are using Prisma ORM v6.14.0 or later, the `$metrics` API is no longer available.
-
-The feature is not supported when using Prisma ORM with the  [query compiler architecture](/orm/prisma-client/setup-and-configuration/no-rust-engine) (setting `engineType` to 'client' in the `generator` block of your `schema.prisma` file).
-
-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. 
+The `metrics` preview feature has been **removed** as of [Prisma ORM v7.0.0](https://github.com/prisma/prisma/releases/tag/7.0.0).  
 
 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.  
 
@@ -50,25 +39,15 @@ Prisma Client provides the following metrics:
   - `prisma_client_queries_active`: The number of currently active Prisma Client queries.
   - `prisma_client_queries_wait`: The number of Prisma Client queries currently waiting for a connection because all connections are in use.
   - `prisma_pool_connections_busy`: The number of currently busy pool connections. These pool connections are currently executing a datasource query.
-  - `prisma_pool_connections_idle`: The number of pool connections that are not currently being used. These pool connections are waiting for the next datasource query to run.
-  - `prisma_pool_connections_open`: The number of [pool connections](/orm/prisma-client/setup-and-configuration/databases-connections/connection-pool#default-connection-pool-size) open.
+  /* Lines 53-55 omitted */
 
 - Histograms (metrics data divided into a collection of values; we call each container in the collection a "bucket"):
-
-  - `prisma_client_queries_wait_histogram_ms`: The time waiting for a pool connection for all Prisma Client queries in ms.
-  - `prisma_client_queries_duration_histogram_ms`: The execution time for all executed Prisma Client queries in ms. This includes the time taken to execute all database queries, and to carry out all database engine activities, such as joining data and transforming data to the correct format.
-  - `prisma_datasource_queries_duration_histogram_ms`: The execution time for all executed Datasource queries in ms.
+/* Lines 57-61 omitted */
 
 You can [add global labels to your metrics data](#global-labels) to help you group and separate your metrics, for example by infrastructure region or server.
 
 ## Prerequisites
 
-:::warning[Version compatibility]
-
-The `metrics` preview feature is **only available in Prisma ORM versions ≤6.13.x**. It has been removed in v6.14.0 and later versions.
-
-:::
-
 To use Prisma Client metrics, you must do the following:
 
 1. [Install compatible Prisma ORM dependencies](#1-install-up-to-date-prisma-orm-dependencies).
@@ -118,167 +97,15 @@ console.log(metrics)
 This returns metrics as follows:
 
 ```json
-{
-  "counters": [
-    {
-      "key": "prisma_client_queries_total",
-      "labels": {},
-      "value": 0,
-      "description": "Total number of Prisma Client queries executed"
-    },
-    {
-      "key": "prisma_datasource_queries_total",
-      "labels": {},
-      "value": 0,
-      "description": "Total number of Datasource Queries executed"
-    },
-    {
-      "key": "prisma_pool_connections_closed_total",
-      "labels": {},
-      "value": 0,
-      "description": "Total number of Pool Connections closed"
-    },
-    {
-      "key": "prisma_pool_connections_opened_total",
-      "labels": {},
-      "value": 1,
-      "description": "Total number of Pool Connections opened"
-    }
-    ...
-  ],
-  "gauges": [
-    ...
-  ],
-  "histograms": [
-    ...
-  ]
-}
+{/* Lines 121-154 omitted */}
 ```
 
 <details>
 
 <summary>Expand to view the full output</summary>
 
 ```json no-copy
-{
-  "counters": [
-    {
-      "key": "prisma_client_queries_total",
-      "labels": {},
-      "value": 2,
-      "description": "Total number of Prisma Client queries executed"
-    },
-    {
-      "key": "prisma_datasource_queries_total",
-      "labels": {},
-      "value": 5,
-      "description": "Total number of Datasource Queries executed"
-    },
-    {
-      "key": "prisma_pool_connections_open",
-      "labels": {},
-      "value": 1,
-      "description": "Number of currently open Pool Connections"
-    }
-  ],
-  "gauges": [
-    {
-      "key": "prisma_client_queries_active",
-      "labels": {},
-      "value": 0,
-      "description": "Number of currently active Prisma Client queries"
-    },
-    {
-      "key": "prisma_client_queries_wait",
-      "labels": {},
-      "value": 0,
-      "description": "Number of Prisma Client queries currently waiting for a connection"
-    },
-    {
-      "key": "prisma_pool_connections_busy",
-      "labels": {},
-      "value": 0,
-      "description": "Number of currently busy Pool Connections (executing a datasource query)"
-    },
-    {
-      "key": "prisma_pool_connections_idle",
-      "labels": {},
-      "value": 21,
-      "description": "Number of currently unused Pool Connections (waiting for the next datasource query to run)"
-    },
-    {
-      "key": "prisma_pool_connections_open",
-      "labels": {},
-      "value": 1,
-      "description": "Number of currently open Pool Connections"
-    }
-  ],
-  "histograms": [
-    {
-      "key": "prisma_client_queries_duration_histogram_ms",
-      "labels": {},
-      "value": {
-        "buckets": [
-          [0, 0],
-          [1, 0],
-          [5, 0],
-          [10, 1],
-          [50, 1],
-          [100, 0],
-          [500, 0],
-          [1000, 0],
-          [5000, 0],
-          [50000, 0]
-        ],
-        "sum": 47.430541000000005,
-        "count": 2
-      },
-      "description": "Histogram of the duration of all executed Prisma Client queries in ms"
-    },
-    {
-      "key": "prisma_client_queries_wait_histogram_ms",
-      "labels": {},
-      "value": {
-        "buckets": [
-          [0, 0],
-          [1, 3],
-          [5, 0],
-          [10, 0],
-          [50, 0],
-          [100, 0],
-          [500, 0],
-          [1000, 0],
-          [5000, 0],
-          [50000, 0]
-        ],
-        "sum": 0.0015830000000000002,
-        "count": 3
-      },
-      "description": "Histogram of the wait time of all Prisma Client Queries in ms"
-    },
-    {
-      "key": "prisma_datasource_queries_duration_histogram_ms",
-      "labels": {},
-      "value": {
-        "buckets": [
-          [0, 0],
-          [1, 0],
-          [5, 2],
-          [10, 2],
-          [50, 1],
-          [100, 0],
-          [500, 0],
-          [1000, 0],
-          [5000, 0],
-          [50000, 0]
-        ],
-        "sum": 47.134498,
-        "count": 5
-      },
-      "description": "Histogram of the duration of all executed Datasource Queries in ms"
-    }
-  ]
-}
+{/* Lines 163-280 omitted */}
 ```
 
 </details>
@@ -313,61 +140,12 @@ let statsd = new StatsD({
   port: 8125,
 })
 
-const diffMetrics = (metrics: Metric<MetricHistogram>[]) => {
-  return metrics.map((metric) => {
-    let prev = 0;
-
-    const diffBuckets = metric.value.buckets.map<MetricHistogramBucket>(
-      (values) => {
-        const [bucket, value] = values
-        const diff = value - prev
-        prev = value
-        return [bucket, diff]
-      }
-    )
-
-    metric.value.buckets = diffBuckets
-    return metric
-  })
-}
+const diffMetrics = (metrics: Metric<MetricHistogram>[]) => {/* Lines 316-331 omitted */}
 
 let previousHistograms: Metric<MetricHistogram>[] = []
 
 
-const statsdSender = async () => {
-  const metrics = await prisma.$metrics.json()
-  
-  metrics.counters.forEach((counter: any) => {
-    statsd.gauge('prisma.' + counter.key, counter.value, (...res) => {})
-  });
-
-  metrics.gauges.forEach((counter: any) => {
-    statsd.gauge('prisma.' + counter.key, counter.value, (...res) => {})
-  })
-
-  if (!previousHistograms.length) {
-    previousHistograms = diffMetrics(metrics.histograms)
-
-    return
-  }
-
-  const diffHistograms = diffMetrics(metrics.histograms);
-
-  diffHistograms.forEach((diffHistogram, histogramIndex) => {
-    diffHistogram.value.buckets.forEach((values, bucketIndex) => {
-      const [bucket, count] = values
-      const [_, prev] =
-        previousHistograms[histogramIndex].value.buckets[bucketIndex]
-      const change = count - prev
-
-      for (let sendTimes = 0; sendTimes < change; sendTimes++) {
-        statsd.timing('prisma.' + diffHistograms.key, bucket)
-      }
-    })
-  })
-
-  previousHistograms = diffHistograms
-}
+const statsdSender = async () => {/* Lines 337-369 omitted */}
 
 setInterval(async () => await statsdSender(), 10000)
 ```
@@ -500,8 +278,7 @@ prisma_datasource_queries_duration_histogram_ms_count 5
 Metrics of type `histogram` expose three different class of values in the Prometheus format:
 
 1. Multiple cumulative counters for observation buckets. These counters are suffixed with `_bucket{le="<upper inclusive bound>"}`. For example, `prisma_datasource_queries_duration_histogram_ms` has a counter exposed as `prisma_datasource_queries_duration_histogram_ms_bucket{le="1"}`
-
-   When an observed value is less than or equal to the upper inclusive bound of a bucket, then Prisma Client metrics increments that bucket by 1. Suppose that you have buckets with the upper inclusive bounds 0, 1, 5, 10, and 50 respectively. If the observed value is 5 then Prisma Client metrics increments the third bucket onwards, because the value is greater than 0 and greater than 1, but less than or equal to 5, 10, and 50.
+/* Lines 502-504 omitted */
 
 2. A single **total sum** for all observed values. This counter is suffixed with `_sum`. For example the total sum of `prisma_datasource_queries_duration_histogram_ms` is exposed as `prisma_datasource_queries_duration_histogram_ms_sum`.
 3. The **count** of the number of events that have been observed. This counter is suffixed with `_count`. For example the total count of `prisma_datasource_queries_duration_histogram_ms` events is exposed as `prisma_datasource_queries_duration_histogram_ms_count`.
@@ -521,7 +298,7 @@ const port = 4000
 const prisma = new PrismaClient()
 
 app.get('/metrics', async (_req, res: Response) => {
-  const metrics = await prisma.$metrics.prometheus()
+  /* Lines 523-524 omitted */
   res.end(metrics)
 })
 
@@ -545,8 +322,7 @@ const register = new prom.Registry()
 prom.collectDefaultMetrics({ register })
 
 app.get('/metrics', async (_req, res: Response) => {
-  const prismaMetrics = await prisma.$metrics.prometheus()
-  const appMetrics = await register.metrics()
+  /* Lines 547-549 omitted */
   res.end(prismaMetrics + appMetrics)
 })
 
@@ -573,29 +349,6 @@ console.log(metrics)
 This returns information in the following format:
 
 ```json highlight=5,11;add
-{
-  "counters": [
-    {
-      "key": "query_total_operations",
-      //add-next-line
-      "labels": { "server": "us_server1", "app_version": "one" },
-      "value": 0,
-      "description": "The total number of operations executed"
-    },
-    {
-      "key": "prisma_datasource_queries_total",
-      //add-next-line
-      "labels": { "server": "us_server1", "app_version": "one" },
-      "value": 0,
-      "description": "The total number of queries executed"
-    },
-    ...
-  ],
-  "gauges": [
-    ...
-  ],
-  "histograms": [
-    ...
-  ]
-}
+{/* Lines 576-599 omitted */}
 ```
+