Troubleshooting

Uptrace version

Before trying anything else, make sure you have the latest Uptrace version.

To see the installed Uptrace version:

uptrace version

You can check the latest available version at GitHub Releases.

Uptrace logs

You can view Uptrace logs using journalctl command:

sudo journalctl -u uptrace -f

To check the status of the service:

sudo systemctl status uptrace

By default, Uptrace only logs failed HTTP requests and failed ClickHouse queries. You can configure Uptrace to log all incoming HTTP requests with an env variable:

HTTPDEBUG=2 uptrace serve

To log all ClickHouse queries:

CHDEBUG=2 uptrace serve

To log all PostgreSQL queries:

PGDEBUG=2 uptrace serve

Database logs

To view ClickHouse logs:

sudo tail -f /var/log/clickhouse-server/clickhouse-server.err.log -n 100

To view PostgreSQL logs:

sudo tail -f /var/log/postgresql/postgresql-17-main.log

Resetting ClickHouse database

If ClickHouse queries are failing, you can try to to reset ClickHouse database:

uptrace ch reset

The check the database status:

uptrace ch status

Resetting PostgreSQL database

Just like with ClickHouse, you can reset the PostgreSQL database that Uptrace uses to store metadata:

uptrace pg reset

The check the database status:

uptrace pg status