Configuring log level
You can control the Pipecat logging level for your deployed agents using thePIPECAT_LOG_LEVEL environment variable. This can be set as a secret or directly in your deployment configuration.
Available log levels:
| Level | Description |
|---|---|
TRACE | The most detailed information for debugging (includes Frame logging) |
DEBUG | Verbose output for debugging (default) |
INFO | General operational information |
WARNING | Warning messages for potential issues |
ERROR | Error messages only |
Agent logs
Agent logs are available via both the CLI and Dashboard. You can view logs for a specific agent by running the following command:Session logging
We recommend using theloguru library for logging within your agent. This will ensure any logging within your agent associated to the session it is running in.
PipecatRunnerArguments object (or subclass alternative) passed to your bot() method:
See the Session Arguments reference for
more additional SessionArgument types.
CPU and memory metrics
Pipecat Cloud tracks CPU and memory usage for each session, which can be helpful for troubleshooting performance issues. You can view these metrics in two ways:Dashboard
Navigate to your agent in the Pipecat Cloud dashboard, then go to Sessions and click on a specific Session ID to view CPU and memory usage graphs.CLI
Use thesessions command with a specific session ID to see CPU and memory usage with sparkline visualizations and percentile summaries: