Add Buggregator to your OTel Collector as one more exporter
Add an otlphttp exporter to your Collector config. Traces and logs from every service show up in Buggregator, and the apps stay as they are.
Tips
Short how-tos, one task each: the answer first, then the steps with code you can copy, then a link to the docs.
8 tips
Add an otlphttp exporter to your Collector config. Traces and logs from every service show up in Buggregator, and the apps stay as they are.
Run FastAPI under opentelemetry-instrument and point the standard OTEL_ env vars at Buggregator. Each request's spans show up as a local waterfall.
Send OTLP/HTTP from your Go service to Buggregator on port 8000. Traces show as a span waterfall and logs link to their trace, on your machine.
Add OpenTelemetry auto-instrumentation to Laravel and send OTLP to Buggregator on port 8000. Each request shows as a span waterfall, no Jaeger needed.
Run your Node service with OpenTelemetry auto-instrumentation and point OTLP at Buggregator. Each request shows as a waterfall of spans locally.
Send OpenTelemetry PHP SDK traces to Buggregator with the standard OTEL_ variables. Each request shows as a waterfall of spans on your machine.
Attach the OpenTelemetry Java agent and point its OTLP endpoint at Buggregator. Each Spring Boot request shows as a span waterfall. No code changes.
Start Buggregator, send one span with curl, and open it as a waterfall. Then point any OTel SDK at port 8000 with three environment variables.