No traces appear in Braintrust
No traces appear in Braintrust
For manual instrumentation, initialize Braintrust with For auto-instrumentation, confirm the Java Agent is attached at startup (see below).
Braintrust.get() and openTelemetryCreate() before you create your provider client, and make calls on the wrapped client returned by the wrap method:#skip-compile
Auto-instrumentation isn't tracing anything
Auto-instrumentation isn't tracing anything
The Java Agent only instruments when it’s attached via the
-javaagent JVM flag at startup. Verify the flag is on the command (or jvmArgs) that actually launches your app.If you run with other Java agents, add the Braintrust agent last in the argument list:Traces are written to the wrong project
Traces are written to the wrong project
Spans route to Or pass it through configuration:
BRAINTRUST_DEFAULT_PROJECT_NAME, which defaults to default-java-project when unset. Set the project in the environment:#skip-compile
BRAINTRUST_API_KEY is required error
BRAINTRUST_API_KEY is required error
The SDK reads your API key from the Or provide it explicitly:
BRAINTRUST_API_KEY environment variable, or from an API key set on the config builder. Set the variable:#skip-compile
Debug setup and API errors
Debug setup and API errors
The SDK logs to the You can also enable SDK debug mode and console trace logging via environment variables:
dev.braintrust namespace through SLF4J. Enable debug logging to surface configuration and export issues. With slf4j-simple, set: