Base Server URL
The BugSnag Performance SDKs will usually default to the correct endpoint, however if you are an On-premise customer or are using a third-party OpenTelemetry SDK the bae server URL for configuring your endpoint is as follows:
Server name
The base server name for this API depends on how you access Insight Hub:
For dashboards on app.bugsnag.com – use
otlp.bugsnag.com
For dashboards on app.insighthub.smartbear.com – use
otlp.insighthub.smartbear.com
For On-premise installations – use
otlp.{{your-domain}}
API key subdomain
When sending spans from an OpenTelemetry SDK or Collector, you must include the Insight Hub API key as a subdomain in the URL (unless you are an On-premise customer):
https://YOUR_API_KEY.my.otlp.server
Your API key can either be a project-level or an organization-level API key. The project-level API key can be found in Project settings in the dashboard. The organization-level endpoint, including API key, is available under Organization settings.
The organization-level API key is designed for use with an OpenTelemetry Collector. When using the organization-level API key, you need to indicate which project a span should be assigned to using a Service Name.
Port
- gRPC:
4317
- HTTP:
4318
The HTTP endpoint can also be accessed on port 443, the default HTTPS port.
Path
When configuring OpenTelemetry SDKs, you sometimes need to omit the path (/v1/traces
) as the SDKs append this. See the per-platform integration guides for details.
Examples
- gRPC:
https://YOUR_API_KEY.my.otlp.server:4317
- HTTP:
https://MY_API_KEY.my.otlp.server:4318/v1/traces