Skip to content

OpenTelemetry (OTLP) Integration

Stream Load Test Metrics over OpenTelemetry

Section titled “Stream Load Test Metrics over OpenTelemetry”

The OpenTelemetry integration exports your live load test metrics over the OpenTelemetry Protocol (OTLP) to any OTLP-compatible backend, so you can watch a test in the same tool you already use for observability. It works with Honeycomb, Grafana Cloud, New Relic, Datadog, Elastic, and any self-hosted OpenTelemetry Collector.

OpenTelemetry Configuration modal in LoadFocus showing name, OTLP endpoint, protocol and headers fields

  1. Open Settings > Integrations.
  2. Click New Integration and choose OpenTelemetry.
  3. Fill in the fields below and click Save integration.
  • Name: A label for this integration, for example Honeycomb HTTP.
  • OTLP endpoint: Where metrics are sent.
    • For HTTP (protobuf), use the base URL including the scheme, for example https://api.honeycomb.io. LoadFocus appends /v1/metrics for you.
    • For gRPC, use host:port, for example api.honeycomb.io:443. If you omit the scheme, https:// is assumed.
  • Protocol: HTTP (protobuf) (the default, works everywhere) or gRPC.
  • Headers (key=value, comma-separated): Pairs used for authentication, for example api-key=YOUR_KEY,x-tenant=team. This is the only secret field and is stored encrypted.
Backend Endpoint (HTTP) Endpoint (gRPC) Headers
Honeycomb https://api.honeycomb.io api.honeycomb.io:443 x-honeycomb-team=INGEST_KEY,x-honeycomb-dataset=DATASET_NAME
Grafana Cloud your stack's OTLP gateway URL not offered on the hosted gateway Authorization=Basic BASE64(instanceID:token)
New Relic https://otlp.nr-data.net (US) or https://otlp.eu01.nr-data.net (EU) otlp.nr-data.net:4317 api-key=LICENSE_KEY
Elastic your APM server OTLP URL your APM server host:8200 Authorization=ApiKey API_KEY
Self-hosted collector https://your-collector:4318 your-collector:4317 optional

For New Relic and Dynatrace, use the dedicated New Relic and Dynatrace integrations instead. They fill in the endpoint for you, check your key when you save, and send delta metrics. Dynatrace needs delta metrics and drops the cumulative metrics this generic integration sends.

  • Use an Ingest Key, created under Environment Settings > API Keys > Ingest. Copy the Key Secret shown once when you create the key, not the shorter Key ID from the list. Sending the Key ID returns unknown API key (HTTP 401).
  • Metrics require the x-honeycomb-dataset header to name the dataset they land in.
  • Give the key the Can create services/datasets permission so the dataset is created on the first metrics that arrive.
  1. Open a JMeter or k6 test and go to its Integrations section.
  2. Select your OpenTelemetry integration from the dropdown.
  3. Save the test, then run it.

Every run tagged with an integration streams its metrics to the configured backend.

Metrics carry the test run name and id, so you can slice by test run.

  • JMeter tests send jmeter.samples (tagged sampler and status, which is ok or ko), jmeter.response_time_ms (tagged sampler) and jmeter.errors (tagged sampler and response_code). The test run is in the resource attributes loadfocus.testrunname and loadfocus.testrunid, next to service.name. JMeter batches and flushes at the end of the run, so its metrics appear once the run finishes.
  • k6 tests send k6's standard metrics such as http_req_duration, http_reqs, vus, and iterations, streamed while the test runs. LoadFocus tags them with testrunname, testrunid, region and machine. Rate metrics such as http_req_failed and checks arrive as one counter each, http_req_failed.total and checks.total, with a condition attribute that is nonzero for a failed request (or a passed check) and zero otherwise; divide the nonzero count by the total to get the rate. Before k6 v2.3.0 (November 2026) they came as two counters, .occurred and .total, so update any dashboard or query built on .occurred.
  • unknown API key or HTTP 401: the credential is wrong or missing. For Honeycomb, confirm you used the Key Secret, not the Key ID.
  • No data in the backend: confirm the destination name (Honeycomb dataset, New Relic account, and so on), confirm the auth header, and remember that JMeter metrics only appear once the run has finished.
  • Endpoint rejected: HTTP endpoints must include the https:// scheme; gRPC endpoints use host:port.
  • The run itself is unaffected: if an integration is misconfigured, the test still runs, it simply exports no metrics.
  • Edit: in Integrations, click the edit icon on the integration to change the name, endpoint, protocol, or headers. Leave the Headers field blank to keep the existing credential; enter a value only when you want to replace it.
  • Remove: click the delete icon on the integration to remove it from your external reporting services.