Tracepanel

Configuration

The environment variables that turn the Java SDK on and off, name your app, move the store and set the thresholds of issues.

Tracepanel for Java reads its settings from environment variables. They are named as in the other SDKs.

Turn it on and off

In Spring Boot, Tracepanel is on whenever its dependency is on the classpath. In Ktor, it is on in development mode. TRACEPANEL_ENABLED=0 turns it off, and TRACEPANEL_ENABLED=1 turns it on.

Settings

VariableDefaultWhat it sets
TRACEPANEL_ENABLEDon in Spring Boot, in development mode in Ktor0 turns Tracepanel off, 1 turns it on
TRACEPANEL_SERVICEspring.application.name, or Ktor's ktor.application.idthe app's name in the console
TRACEPANEL_DIR.tracepanelthe store, where the agent keeps the traces
TRACEPANEL_ROOTthe current directorythe project's directory, that paths in stacks are relative to
TRACEPANEL_MAX_TRACES2000how many traces the agent keeps
TRACEPANEL_AGENT_BINthe agent the SDK downloadsthe agent to start, such as a build of your own
TRACEPANEL_AGENTautoan agent that runs elsewhere, as tcp:host:port, which Tracepanel never starts
TRACEPANEL_CACHE_DIR~/.cache/tracepanelwhere the downloaded agent is kept

Thresholds

The agent finds the issues by these thresholds:

VariableDefaultWhat it sets
TRACEPANEL_N_PLUS_ONE_THRESHOLD3how many repeats make an N+1
TRACEPANEL_N_PLUS_ONE_MIN_MS5for Redis and other fast stores, the time the repeats must take together
TRACEPANEL_SLOW_SQL_MS100a slow query, SQL or MongoDB
TRACEPANEL_SLOW_HTTP_MS500a slow outgoing HTTP call
TRACEPANEL_LONG_TRANSACTION_MS500a long transaction
TRACEPANEL_QUEUE_WAIT_MS1000a task that waited long for a worker
TRACEPANEL_LARGE_RESULT_ROWS1000a query without a LIMIT that read too many rows

On this page