Skip to content

Commit

Permalink
polished orm
Browse files Browse the repository at this point in the history
  • Loading branch information
nikolasburk committed Dec 4, 2023
1 parent 3af8653 commit fa2c41b
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ datasource db {

#### Viewing the connection pool size

The number of connections Prisma Client uses can be viewed using [logging](/orm/prisma-client/setup-and-configuration/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 [metrics](/orm/prisma-client/observability-and-logging/metrics).

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.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This guide describes ways to optimize query performance, debug performance issue

## Debugging performance issues

To help you debug and diagnose performance issues, you can [log query events at client level](/orm/prisma-client/setup-and-configuration/logging#event-based-logging), which allows you to see the generated queries, parameters, and durations.
To help you debug and diagnose performance issues, you can [log query events at client level](/orm/prisma-client/observability-and-logging/logging#event-based-logging), which allows you to see the generated queries, parameters, and durations.

Alternatively, if you are only interested in the time taken to run a query, you can implement [logging middleware](/orm/prisma-client/client-extensions/middleware/logging-middleware).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ You can enable debugging output in Prisma Client via the [`DEBUG`](/orm/referenc

<Admonition type="info">

Prisma Client can be configured to log warnings, errors and information related to queries sent to the database. See [Configuring logging](/orm/prisma-client/setup-and-configuration/logging) for more information.
Prisma Client can be configured to log warnings, errors and information related to queries sent to the database. See [Configuring logging](/orm/prisma-client/observability-and-logging/logging) for more information.

</Admonition>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ const prisma = new PrismaClient({

### <inlinecode>log</inlinecode>

Determines the type and level of logging. See also: [Logging](/orm/prisma-client/setup-and-configuration/logging)
Determines the type and level of logging. See also: [Logging](/orm/prisma-client/observability-and-logging/logging)

#### Options

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,7 @@ const prisma = new PrismaClient({
})
```

Learn more about [Debugging](/orm/prisma-client/debugging-and-troubleshooting/debugging) and [Logging](/orm/prisma-client/setup-and-configuration/logging).
Learn more about [Debugging](/orm/prisma-client/debugging-and-troubleshooting/debugging) and [Logging](/orm/prisma-client/observability-and-logging/logging).

## Configuring the query engine

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ If you don't have the time to create a full reproduction of the issue, please in

### Include logging and debugging output

Please make sure to include _any_ [logging](/orm/prisma-client/setup-and-configuration/logging) and [debugging](/orm/prisma-client/debugging-and-troubleshooting/debugging) output in the issue that may help to identify the problem.
Please make sure to include _any_ [logging](/orm/prisma-client/observability-and-logging/logging) and [debugging](/orm/prisma-client/debugging-and-troubleshooting/debugging) output in the issue that may help to identify the problem.

**Setting the `DEBUG` env var**

Expand Down

0 comments on commit fa2c41b

Please sign in to comment.