Debugging Uptrace issues

Uptrace version

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

To see the installed Uptrace version:

uptrace version

Then check the latest available version at GitHub Releasesopen in new window.

Logging

You can view Uptrace logs using journalctl command:

sudo journalctl -u uptrace -f

By default, Uptrace only logs failed HTTP requests and failed ClickHouse queries. You can configure Uptrace to log all requests and queries by changing the config at /etc/uptrace/uptrace.yml:

# Enable to log HTTP requests and ClickHouse queries.
debug: true

Or change DEBUG environment variable in /etc/uptrace/uptrace.conf:

# Configures Uptrace logging level.
#   - 0 - disable logging
#   - 1 - log failed requests and queries
#   - 2 - log all requests and queries
DEBUG=2

And then restart Uptrace:

sudo systemctl restart uptrace

To check the status of the service:

sudo systemctl status uptrace

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 db reset

The check the database status:

uptrace db status
Last Updated: