# Quieter startup and workflow logs

> Agno debug logs now leave out PostgreSQL connection-pool chatter. Log output outside a terminal is plain text, and workflow step summaries move to DEBUG.

- Published: 2026-09-08
- Author: Ashpreet Bedi
- Categories: Changelog
- Canonical: https://www.agno.com/articles/quieter-startup-and-workflow-logs
- Markdown: https://www.agno.com/articles/quieter-startup-and-workflow-logs.md

Agno now leaves PostgreSQL connection-pool diagnostics under SQLAlchemy's own `sqlalchemy.pool` logger, where you can still turn them on. With `AGNO_DEBUG=True`, the pools used to inherit Agno's logger and flood container output with every checkout, pre-ping and reset.

Outside a terminal, Agno now writes plain, unwrapped log lines, so container and log-aggregator output reads line by line. Terminal and Jupyter output keeps its Rich formatting. Agno logging also keeps working when stdout is missing or your application has configured its own loggers.

Agno's startup messages are shorter. Queue acceptance stays at INFO. Workflow lifecycle, step and outcome summaries move to DEBUG with their run IDs.

```text
INFO    Workflow queued: sync-docs run=<run-id>
DEBUG   Workflow started: sync-docs run=<run-id>
DEBUG   Step started: sync-docs step=1/1 streaming=true
DEBUG   Workflow completed: sync-docs run=<run-id> duration=2.31s
```

Learn more about [debug mode](https://docs.agno.com/agents/debugging-agents) and [custom logging](https://docs.agno.com/custom-logging) in the documentation.