opentelemetry-collector-contrib: [exporter/datadog]: Failed to retrieve metadata

What happened?

Some warning messages appear in our logs after upgrading to version v0.60.0.
We don't want to send host metrics to Datadog and it seems to be mandatory with the latest version.

Collector version

v0.60.0

Environment information

Gateway deployment mode on Google GKE autopilot.

OpenTelemetry Collector configuration

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
processors:
  memory_limiter:
    check_interval: 1s
    limit_mib: 1500
    spike_limit_mib: 500
  resource:
    attributes:
      - key: deployment.environment
        value: test
        action: upsert
      - key: cloud.region
        value: test
        action: upsert
  batch:
    send_batch_size: 256
    send_batch_max_size: 512
exporters:
  datadog:
    api:
      key: ${DD_API_KEY}
      site: datadoghq.eu
    metrics:
      sums:
        cumulative_monotonic_mode: to_delta
      histograms:
        mode: distributions
        send_count_sum_metrics: true
      resource_attributes_as_tags: true
service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [resource, batch]
      exporters: [datadog]

Log output

[Debug] Error fetching info for pid 1: open /etc/passwd: no such file or directory
warn	gohai/gohai.go:66	Failed to retrieve platform metadata	{"kind": "exporter", "data_type": "metrics", "name": "datadog", "error": "exec: \"uname\": executable file not found in $PATH"}
warn	gohai/gohai.go:47	Failed to retrieve filesystem metadata	{"kind": "exporter", "data_type": "metrics", "name": "datadog", "error": "df failed to collect filesystem data: %!s(<nil>)"}

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 5
Comments: 21 (7 by maintainers)

Most upvoted comments

I still see this same issue on messages running version 0.67.0,


2023-03-03T22:20:42.839Z        info    gohai/gohai.go:47       Failed to retrieve filesystem metadata  {"kind": "exporter", "data_type": "traces", "name": "datadog", "error": "df failed to collect filesystem data: %!s(<nil>)"}
2023-03-03T22:20:42.840Z        info    gohai/gohai.go:66       Failed to retrieve platform metadata    {"kind": "exporter", "data_type": "traces", "name": "datadog", "error": "exec: \"uname\": executable file not found in $PATH"}

brunocrt on Mar 3, 2023

@husseinraoouf to clarify, this error message shouldn’t stop datadog exporter from reporting metrics or have any other issues. This is happening as the docker image doesn’t have required dependencies.

There are few routes we can take.

Classify the warning as info, with additional information that it doesn’t impact the exporter. (preferred )
Add the dependencies to the official built , might be hard to get approval
Remove these metadata collector (least preferred )

@mx-psi let me know your thoughts on same.

dineshg13 on Nov 14, 2022

I’m running the Collector with v0.71.0 and see these log messages. Is the issue going to be solved? I don’t see any Infrastructure metrics in my spans since I updated my OTel Collector.

ronenl3 on Feb 19, 2023

Hi guys, did you found a solution for this ? I’m not able to retrieve metadata in DD (can see hosts and metrics, but without k8s data), i have this error

image: otel/opentelemetry-collector-contrib:0.84.0

info    gohai/gohai.go:35    Failed to retrieve filesystem metadata    {"kind": "exporter", "data_type": "metrics", "name": "datadog", "error": "df failed to collect filesystem data: %!s(<nil>)"}
info    gohai/gohai.go:54    Failed to retrieve platform metadata    {"kind": "exporter", "data_type": "metrics", "name": "datadog", "error": "exec: \"uname\": executable file not found in $PATH"}

VinxItak on Sep 11, 2023

I don’t see any Infrastructure metrics in my spans since I updated my OTel Collector.

Could you open a separate issue for this? I don’t think your issue is related to the log messages here

mx-psi on Feb 20, 2023

Hi @inigohu . I am interested to work on this could you please assign this to me ??

Sunilwali679 on Oct 3, 2022