Open andrewkroh opened 7 months ago
Also seeing this, 8.12.2.
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)
Still being observed
{"log.level":"error","@timestamp":"2024-10-23T15:46:07.282Z","message":"add_cloud_metadata: received error failed with http status code 404","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"log-default","type":"log"},"log":{"source":"log-default"},"log.logger":"add_cloud_metadata","log.origin":{"file.line":190,"file.name":"add_cloud_metadata/providers.go","function":"github.com/elastic/beats/v7/libbeat/processors/add_cloud_metadata.(addCloudMetadata).fetchMetadata"},"service.name":"filebeat","ecs.version":"1.6.0","ecs.version":"1.6.0"} {"log.level":"error","@timestamp":"2024-10-23T15:46:07.795Z","message":"add_cloud_metadata: received error failed with http status code 404","component":{"binary":"metricbeat","dataset":"elastic_agent.metricbeat","id":"system/metrics-default","type":"system/metrics"},"log":{"source":"system/metrics-default"},"log.logger":"add_cloud_metadata","log.origin":{"file.line":190,"file.name":"add_cloud_metadata/providers.go","function":"github.com/elastic/beats/v7/libbeat/processors/add_cloud_metadata.(addCloudMetadata).fetchMetadata"},"service.name":"metricbeat","ecs.version":"1.6.0","ecs.version":"1.6.0"}
I think that the
add_cloud_metadata
is now logging errors for things that are expected to fail during normal cloud platform discovery. It seems very noisy.It has been happening since at least 8.11.4.
Here are the raw logs from my 8.13.0 Elastic Agent running on AWS EKS.