FAQs

​

What is the BugByBug OTLP endpoint?

Use https://nexus.bugbybug.com/v1/traces as your OTLP HTTP trace endpoint.

​

Which authentication header should I use?

You can use either Authorization: Bearer <YOUR_API_KEY> or x-api-key: <YOUR_API_KEY>, depending on your language or exporter.

​

Does BugByBug support OpenTelemetry?

Yes. BugByBug works with OpenTelemetry traces sent through standard OTLP HTTP exporters.

​

Do I need a collector?

No. You can send traces directly to BugByBug if your exporter supports OTLP HTTP.

​

Why don’t I see errors in BugByBug?

Make sure you record the exception on the active span and set the span status to error before the span ends.

​

Which languages are supported?

BugByBug can receive traces from any language supported by the OpenTelemetry ecosystem.

​

What should I use for service.name?

Use a stable name for your application or service so your traces are easy to identify in BugByBug.

​

How do I verify that BugByBug is receiving data?

Trigger a test error in your application or send a manual test trace to the ingestion endpoint.