# Export traces to Bronto - Checkly Docs

> Send Checkly traces to Bronto with an Ingestion API key.

Source: https://www.checklyhq.com/docs/integrations/observability/traces/bronto/

---

Traces

# Export traces to Bronto

Send Checkly traces to Bronto with an Ingestion API key.

Before you start, read the prerequisites on the [OTLP export page](https://www.checklyhq.com/docs/integrations/observability/traces/otlp) and check [what is sent](https://www.checklyhq.com/docs/integrations/observability/traces/otlp#what-is-sent).
This page only covers the values Bronto needs.

- Get the endpoint for your Bronto region. EU is `https://ingestion.eu.bronto.io/v1/traces` and US is `https://ingestion.us.bronto.io/v1/traces`. Checkly posts to exactly the URL you enter, so keep the `/v1/traces` path.

- Get the key. In Bronto, open **Settings** > **API Keys**, select **Add API key**, name it and give it the **Ingestion Role**. Copy the key right away, because Bronto shows it once.

- Paste the values into Checkly. On the [Traces settings page](https://app.checklyhq.com/settings/account/traces), turn on **Enable exporting traces**, paste the URL, add the header below, and save. Header name Value `x-bronto-api-key` ` `

- Run a check, or wait for its schedule. Ad hoc runs from the check editor are exported too.

- Find the spans. In Bronto, open **Tracing**. The spans appear under service `checkly`, named after the check.

If no spans arrive, check that the export is saved, that the header name is exactly `x-bronto-api-key` and that the key carries the Ingestion role. Then check the region: an EU key sent to the US host is rejected, and the other way round.
When your own services are instrumented and report to the same Bronto account, their spans nest under the check run with no further setup. [Correlate with your application’s traces](https://www.checklyhq.com/docs/integrations/observability/traces/otlp#correlate-with-your-application%E2%80%99s-traces) covers the headers that make this work.
Build conditions with **Filter**: pick the field `Span:checkly.check.status`, the comparison **does not equal** and the value `PASSED` to list the runs that did not pass, and add `$service.name` equals `checkly` to leave your own services out.

Bronto documents the endpoints in [Bronto Ingestion Endpoints](https://docs.bronto.io/getting-started/bronto-endpoints) and this setup in [Checkly synthetic monitoring with OpenTelemetry](https://docs.bronto.io/integrations/checkly).
To see failed runs, filter on the attribute `checkly.check.status` with the value `FAILED`.
The [OTLP export page](https://www.checklyhq.com/docs/integrations/observability/traces/otlp) has the span schema.

Was this page helpful?

[Suggest edits](https://github.com/checkly/docs/edit/main/integrations/observability/traces/bronto.mdx)[Raise issue](https://github.com/checkly/docs/issues/new?title=Issue%20on%20docs&body=Path:%20/integrations/observability/traces/bronto)

[Send traces, RUM and alerts to Coralogix Previous](https://www.checklyhq.com/docs/integrations/observability/coralogix)[Export traces to Chronosphere Next](https://www.checklyhq.com/docs/integrations/observability/traces/chronosphere)

[x](https://x.com/checklyhq)[github](https://github.com/checkly)[linkedin](https://linkedin.com/company/checkly)

[Powered by This documentation is built and hosted on Mintlify, a developer documentation platform](https://www.mintlify.com/?utm_campaign=poweredBy&utm_medium=referral&utm_source=checkly-422f444a)