Debugging (Prisma ORM v6) (/docs/orm/v6/prisma-client/debugging-and-troubleshooting/debugging)
For the complete Prisma documentation index, see llms.txt. A markdown version of any docs page is available by appending
.mdto its URL.
This page explains how to enable debugging output for Prisma Client by setting the DEBUG environment variable.
Location: ORM > v6 > Prisma Client > Debugging and Troubleshooting > Debugging
You can enable debugging output in Prisma Client and Prisma CLI via the DEBUG environment variable. It accepts two namespaces to print debugging output:
prisma:engine: Prints relevant debug messages happening in a Prisma ORM engineprisma:client: Prints relevant debug messages happening in the Prisma Client runtimeprisma*: Prints all debug messages from Prisma Client or CLI*: Prints all debug messages
[!NOTE] Prisma Client can be configured to log warnings, errors and information related to queries sent to the database. See Configuring logging for more information.
Setting the DEBUG environment variable
Section titled “Setting the DEBUG environment variable”Here are examples for setting these debugging options in bash:
# enable only `prisma:engine`-level debugging output
export DEBUG="prisma:engine"
# enable only `prisma:client`-level debugging output
export DEBUG="prisma:client"
# enable both `prisma-client`- and `engine`-level debugging output
export DEBUG="prisma:client,prisma:engine"To enable all prisma debugging options, set DEBUG to prisma*:
export DEBUG="prisma*"On Windows, use set instead of export:
set DEBUG="prisma*"To enable all debugging options, set DEBUG to *:
export DEBUG="*"Related pages
Section titled “Related pages”Handling exceptions and errors: This page covers how to handle exceptions and errorsTroubleshooting binary size and deployment issues: This page covers how to resolve large bundle sizes, slow builds, and deployment errors caused by Prisma ORM Rust engine binaries