Skip to main content
BotGauge accepts plain OpenTelemetry, so you can forward traces without installing the BotGauge SDK. Point any OTLP/HTTP exporter at the endpoint below with your key as a Bearer token and gzip compression. That’s the same thing the SDK sends.
Spans sent this way reach BotGauge as your instrumentation produced them. They carry no botgauge.session.id or botgauge.agent.id attributes, and nothing gets masked. Use the SDK if you need session and agent identity or PII masking.

In code (Python)

Add an OTLP exporter to your own tracer provider.
terminal
raw_otlp.py

Environment variables only

OpenTelemetry’s own launcher, opentelemetry-instrument, configures the exporter from environment variables and turns on the instrumentors you’ve installed. This example traces an unmodified LangChain app through the OpenInference LangChain instrumentor. Install your framework’s instrumentor instead. See the instrumentor packages.
terminal
terminal
app.py
terminal
The header value is URL-encoded. %20 is the space after Bearer.

Forward traces from any exporter

Send your OpenTelemetry traces directly to BotGauge.

Try BotGauge →

Through an OpenTelemetry Collector

If your apps already send to a Collector, add BotGauge as an exporter. The key stays in the Collector, so your apps don’t need it. Start the Collector with BOTGAUGE_API_KEY set.
collector.yaml
terminal
Then point your app at the Collector, for example with the same app.py and opentelemetry-instrument.
terminal
This was tested with the OpenTelemetry Collector core build 0.162.0. That build accepts the HTTP exporter as otlphttp (used here) or otlp_http.