OBI Exported Metrics miss attributes: otelcol error log unable to get service name from resource metric with attributes: map[]

[dingfeng2]

I deploy using docker-compose, and configurate environments in OBI container

environment:
      OTEL_EBPF_SERVICE_NAMESPACE: integration-test
      OTEL_SERVICE_NAME: otel-ebpf-instrument-test
      OTEL_RESOURCE_ATTRIBUTES: 'service.name=otel-ebpf-instrument-test,service.namespace=integration-test'
      OTEL_EBPF_METRICS_FEATURES: application

In Opentelemetry Collector:

2026-03-18T06:37:12.032Z        error   loadbalancingexporter@v0.147.0/metrics_exporter.go:112  failed to export metric {"resource": {"service.instance.id": "8b43ab1a-1f07-4c9a-a1b9-5d2c77745f1a", "service.name": "otelcol_lb_test", "service.version": "0.147.0"}, "otelcol.component.id": "loadbalancing", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "error": "unable to get service name from resource metric with attributes: map[]"}

It seems to be missing the "attributes" section, docker image is

ghcr.io/open-telemetry/opentelemetry-ebpf-instrumentation/ebpf-instrument@sha256:7a8a40ac3640423af2f114e34ab81271d893bb8b39378022a88136e4608fee99

Please give me some guidance, tks

[mariomac]

Hi @dingfeng2 !

I guess you are setting these variables in the OBI container. Please try this:

• Remove the following variables from the OBI container: OTEL_EBPF_SERVICE_NAMESPACE, OTEL_SERVICE_NAME, OTEL_RESOURCE_ATTRIBUTES
• Add the following environment variable to the container of the application you are instrumenting:

      OTEL_RESOURCE_ATTRIBUTES: 'service.name=otel-ebpf-instrument-test,service.namespace=integration-test'

[dingfeng2]

tks, @mariomac
I have added the following environment variable OTEL_RESOURCE_ATTRIBUTES to the container of my application, but it has not taken effect. The Traces data contains Resource Attributes, but the Metrics data does not.

[mariomac]

@dingfeng2 can I see your complete OBI configuration? Thanks!

[dingfeng2]

@mariomac , I deploy using docker-compose.
docker-compose.yml

version: '3.8'                                                                                                                                                   
services:
  otel-ebpf-instrument:
    image: ghcr.io/open-telemetry/opentelemetry-ebpf-instrumentation/ebpf-instrument@sha256:7a8a40ac3640423af2f114e34ab81271d893bb8b39378022a88136e4608fee99
    container_name: otel-ebpf-instrument
    hostname: otel-ebpf-instrument
    pid: 'host'
    privileged: true
    ports:
      - 1894:1894
    environment:
      OTEL_EBPF_LOG_LEVEL: INFO
      # OTEL_EBPF_SERVICE_NAMESPACE: integration-test
      # OTEL_SERVICE_NAME: otel-ebpf-instrument-test
      OTEL_EBPF_OPEN_PORT: 31883
      # OTEL_RESOURCE_ATTRIBUTES: 'service.name=otel-ebpf-instrument-test,service.namespace=integration-test'
      # OTEL_EBPF_EXTRA_SPAN_RESOURCE_ATTRIBUTES: 'service.name=otel-ebpf-instrument-test'
      OTEL_EXPORTER_OTLP_TRACES_ENDPOINT: http://localhost:4317
      OTEL_EXPORTER_OTLP_TRACES_PROTOCOL: grpc
      OTEL_EXPORTER_OTLP_METRICS_ENDPOINT: http://localhost:4317
      OTEL_EXPORTER_OTLP_METRICS_PROTOCOL: grpc
      OTEL_EBPF_METRICS_FEATURES: application
      OTEL_EBPF_METRICS_INTERVAL: 10s
      OTEL_EBPF_METRICS_INSTRUMENTATIONS: http
      OTEL_EBPF_PROMETHEUS_PORT: 1894
      OTEL_EBPF_PROMETHEUS_PATH: /metrics

[mariomac]

Thank you! This seems to me as an issue with your OTEL collector configuration. Can I see it so we can try to reproduce locally?

In addition, can you run it with OTEL_EBPF_SDK_LOG_LEVEL=debug and show us the logs output of OBI? This way we can see exactly what is OBI trying to export

[dingfeng2]

@mariomac sorry, I cannot provide my OTEL configuration, but i run it with OTEL_EBPF_SDK_LOG_LEVEL=debug.

This is my the logs output of OBI:

time=2026-03-20T00:38:22.554Z level=DEBUG msg="OTLP/gRPC exporter export" component=otel.BatchSpanProcessor Data="&{Resource:host.id=,host.name=otel-ebpf-instrument,os.type=linux,service.instance.id=otel-ebpf-instrument:1119327,service.name=otel-ebpf-instrument-test,service.namespace=integration-test,telemetry.distro.name=opentelemetry-ebpf-instrumentation,telemetry.distro.version=,telemetry.sdk.language=cpp,telemetry.sdk.name=opentelemetry,telemetry.sdk.version=v1.42.0 ScopeMetrics:[{Scope:{Name:go.opentelemetry.io/obi Version: SchemaURL: Attributes:{hash:0 data:}} Metrics:[{Name:http.server.request.duration Description: Unit:s Data:{DataPoints:[{Attributes:{hash:7326018828914991057 data:[{Key:http.request.method Value:{vtype:4 numeric:0 stringly:GET slice:}} {Key:http.response.status_code Value:{vtype:2 numeric:200 stringly: slice:}} {Key:http.route Value:{vtype:4 numeric:0 stringly:/metrics slice:}} {Key:server.address Value:{vtype:4 numeric:0 stringly:otel-ebpf-instrument-test slice:}} {Key:server.port Value:{vtype:2 numeric:36080 stringly: slice:}} {Key:service.name Value:{vtype:4 numeric:0 stringly:otel-ebpf-instrument-test slice:}} {Key:service.namespace Value:{vtype:4 numeric:0 stringly:integration-test slice:}}]} StartTime:2026-03-20 00:38:12.55106039 +0000 UTC m=+7.267342960 Time:2026-03-20 00:38:22.55188261 +0000 UTC m=+17.268165241 Count:1 Bounds:[0 0.005 0.01 0.025 0.05 0.075 0.1 0.25 0.5 0.75 1 2.5 5 7.5 10] BucketCounts:[0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0] Min:{value:0.003401333 valid:true} Max:{value:0.003401333 valid:true} Sum:0.003401333 Exemplars:[{FilteredAttributes:[] Time:2026-03-20 00:38:21.553165634 +0000 UTC m=+16.269448203 Value:0.003401333 SpanID:[141 122 127 32 133 176 233 34] TraceID:[145 91 223 213 125 101 201 127 178 251 9 91 82 199 82 188]}]}] Temporality:CumulativeTemporality}}

The value of Resource looks problematical

If you want to reproduce locally, i used the loadbalance component in my OTEL configuration, which can be introduced into the exporter.

exporter:
  loadbalancing:
    routing_key: "service"

[mariomac]

This seems like an OTEL Collector configuration issue.

OBI is using the OTEL service.name attribute while it seems your collector is expecting an unexisting field named service.

You should either:

• Using service.name as routing key.
  or
• Configure the collector to rewrite the service.name attribute as service before being exported.

[dingfeng2]

@mariomac, thanks!
But it is using service as routing key in OTEL Collector Docs.

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/loadbalancingexporter/README.md

[dingfeng2]

hi，@mariomac
This isn't my OTEL Collector 's problem. Whenever the other components I use operate on Metric's ResourceAttributes, this error occurs. I suggest you check the exported metric data.