Skip to main content
Bronto accepts OpenTelemetry metrics over OTLP/HTTP. You can export metrics directly from an OpenTelemetry SDK or route them through an OpenTelemetry Collector before forwarding them to Bronto.
OTLP metrics ingestion is in public beta.
Bronto recommends enabling logs, metrics, and traces together so every service has a consistent telemetry pipeline. If you only need metrics, OpenTelemetry lets you enable the metrics exporter and pipeline independently.

​
Supported metric types

Bronto supports ingestion of sum and histogram metrics as delta or cumulative. Delta is strongly recommended to get the best value from the current set of supported functions.
The Metric Explorer does not currently provide a Rate function. To visualize a rate, emit a rate metric from the source or precompute it in your telemetry pipeline before exporting it to Bronto.

​
Prerequisites

Before you begin, you need:
  • a Bronto API key with ingestion permissions
  • your Bronto region: eu or us
  • an application instrumented with an OpenTelemetry metrics SDK, or an OpenTelemetry Collector receiving metrics

​
Endpoint and authentication

Use the metrics endpoint for your Bronto region: Both endpoints accept OTLP/HTTP protobuf over HTTPS on port 443. Every request must include:

​
Send metrics through an OpenTelemetry Collector

Configure an OTLP receiver and an OTLP/HTTP exporter that targets the Bronto metrics endpoint:
The example uses the standard Collector receiver ports: 4317 for OTLP/gRPC and 4318 for OTLP/HTTP. A same-host application typically exports OTLP/HTTP metrics to http://localhost:4318/v1/metrics; replace the host, port, protocol, and TLS settings when your deployment differs.
otel-config.yaml
Replace <REGION> with eu or us. If your Collector also sends logs and traces, add the Bronto metrics exporter to its metrics pipeline and keep the existing signal pipelines. Each signal uses its own endpoint.

​
Send metrics directly from an SDK

For SDKs that support OTLP/HTTP configuration through environment variables:
Configure a meter provider and periodic metric reader in your application. Use the language-specific OpenTelemetry guides for SDK setup.

​
Resource attributes

Set resource attributes once and share them across logs, metrics, and traces:
At minimum, set service.name so metrics can be associated with the service that emitted them.

​
Verify metric delivery

  1. Open Metric Explorer in Bronto.
  2. Select a recently emitted metric.
  3. Confirm its service and resource attributes are present.
  4. Compare the latest timestamp with the export interval configured in your SDK or Collector.

​
Troubleshooting

If metrics do not appear:
  • confirm the endpoint matches your Bronto region and ends in /v1/metrics
  • confirm the x-bronto-api-key header is present
  • confirm the Collector has an enabled metrics pipeline
  • check that the SDK has a metric reader and exporter configured
  • check Collector logs for rejected exponential histograms
  • allow at least one SDK export interval before checking Metric Explorer
For a combined logs, metrics, and traces setup, see Connect OpenTelemetry Collector to Bronto.

​
Further reading