# Filebeat: add\_cloud\_metadata: hosting provider type not detected

**URL:** <https://discuss.elastic.co/t/filebeat-add-cloud-metadata-hosting-provider-type-not-detected/365395>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 22, 2024, 3:07pm UTC](https://discuss.elastic.co/t/filebeat-add-cloud-metadata-hosting-provider-type-not-detected/365395 "2024-08-22T15:07:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebagarayco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebagarayco/32/136993_2.png) [@sebagarayco](https://discuss.elastic.co/u/sebagarayco)\
**Post date:** [August 22, 2024, 3:07pm UTC](https://discuss.elastic.co/t/filebeat-add-cloud-metadata-hosting-provider-type-not-detected/365395/1 "2024-08-22T15:07:23Z")

</div>

We are having issues while trying to use add\_cloud\_metadata in AKS clusters. Filebeat version is 8.15 and it's running AKS 1.28 clusters.

Our config looks like this:

```auto
    processors:
    - add_cloud_metadata:
        providers: ['azure']
...
            - name: AZURE_CLIENT_ID
              valueFrom:
                secretKeyRef:
                  name: azcli
                  key: client
            - name: AZURE_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  name: azcli-pass
                  key: password
            - name: AZURE_TENANT_ID
              value: "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"

```

And the logs are showing:

```auto
filebeat {"log.level":"warn","@timestamp":"2024-08-22T14:47:43.539Z","log.logger":"add_cloud_metadata","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/processors/add_cloud_metadata.(*azureMetadataFetcher).fetchMetadata","file.name":"add_cloud_metadata/provider_azure_vm.go","file.line":142},"message":"Failed to get additional AKS Cluster meta: failed to get AKS cluster name and ID: failed to advance page: context deadline exceeded","service.name":"filebeat","ecs.version":"1.6.0"}
filebeat {"log.level":"info","@timestamp":"2024-08-22T14:47:43.539Z","log.logger":"add_cloud_metadata","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/processors/add_cloud_metadata.(*addCloudMetadata).init.func1","file.name":"add_cloud_metadata/add_cloud_metadata.go","file.line":100},"message":"add_cloud_metadata: hosting provider type not detected.","service.name":"filebeat","ecs.version":"1.6.0"}

```

IMDS endpoint is accesible from Filebeat pods / No network policies in place:

```auto
/usr/share/filebeat# curl -s -H "Metadata:true" "http://169.254.169.254/metadata/instance?api-version=2021-01-01" | jq .compute.azEnvironment
"AzurePublicCloud"

```

---

<div class="post-metadata">

**Author:** ![Oolong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oolong/32/136182_2.png) [@Oolong](https://discuss.elastic.co/u/Oolong)\
**Post date:** [October 9, 2024, 6:56pm UTC](https://discuss.elastic.co/t/filebeat-add-cloud-metadata-hosting-provider-type-not-detected/365395/2 "2024-10-09T18:56:49Z")

</div>

Did you manage to solve this by any chance ?

---

<div class="post-metadata">

**Author:** ![sebagarayco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebagarayco/32/136993_2.png) [@sebagarayco](https://discuss.elastic.co/u/sebagarayco)\
**Post date:** [November 18, 2024, 2:37pm UTC](https://discuss.elastic.co/t/filebeat-add-cloud-metadata-hosting-provider-type-not-detected/365395/3 "2024-11-18T14:37:17Z")

</div>

Yes sir! related to [[AKS] Failed to get additional AKS Cluster meta](https://discuss.elastic.co/t/aks-failed-to-get-additional-aks-cluster-meta/365932)

After adding resources and removing `AZURE_` from env names it started working.