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

**URL:** <https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 24, 2019, 3:13pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164 "2019-06-24T15:13:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![markov](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markov](https://discuss.elastic.co/u/markov)\
**Post date:** [June 24, 2019, 3:13pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164/1 "2019-06-24T15:13:18Z")

</div>

i'm getting this error while starting filebeat after an update from 6.x to 7.x :  
i have logstash filters but it's sending the machine informations  
any ideas !!

```
2019-06-24T12:48:48.741+0100 DEBUG [beat] instance/beat.go:623 Beat metadata path: /var/lib/filebeat/meta.json
2019-06-24T12:48:48.741+0100 INFO instance/beat.go:579 Beat ID: 84176e08-7017-4eee-80f3-3e583f391ff5
2019-06-24T12:48:48.741+0100 INFO [index-management.ilm] ilm/ilm.go:129 Policy name: filebeat-7.1.1
2019-06-24T12:48:48.742+0100 DEBUG [filters] add_cloud_metadata/add_cloud_metadata.go:164 add_cloud_metadata: starting to fetch metadata, timeout=3s
2019-06-24T12:48:48.945+0100 DEBUG [filters] add_cloud_metadata/add_cloud_metadata.go:196 add_cloud_metadata: received disposition for qcloud after 202.91057ms. result=[provider:qcloud, error=failed requesting qcloud metadata: Get http://metadata.tencentyun.com/meta-data/instance-id: dial tcp: lookup metadata.tencentyun.com on 10.96.36.114:53: no such host, metadata={}]
2019-06-24T12:48:51.743+0100 DEBUG [filters] add_cloud_metadata/add_cloud_metadata.go:196 add_cloud_metadata: received disposition for openstack after 3.000177064s. result=[provider:openstack, error=failed requesting openstack metadata: Get http://xxx.xxx.xxx.254/2009-04-04/meta-data/instance-type: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers), metadata={}]
2019-06-24T12:48:51.743+0100 DEBUG [filters] add_cloud_metadata/add_cloud_metadata.go:203 add_cloud_metadata: timed-out waiting for all responses
2019-06-24T12:48:51.743+0100 DEBUG [filters] add_cloud_metadata/add_cloud_metadata.go:167 add_cloud_metadata: fetchMetadata ran for 3.000261888s
2019-06-24T12:48:51.743+0100 INFO add_cloud_metadata/add_cloud_metadata.go:346 add_cloud_metadata: hosting provider type not detected.
2019-06-24T12:48:51.743+0100 DEBUG [processors] processors/processor.go:66 Processors: add_host_metadata=[netinfo.enabled=[false], cache.ttl=[5m0s]], add_cloud_metadata=null
```

---

<div class="post-metadata">

**Author:** ![pmercado](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@pmercado](https://discuss.elastic.co/u/pmercado)\
**Post date:** [June 24, 2019, 3:49pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164/2 "2019-06-24T15:49:17Z")

</div>

Hi @markov,

I guess the error is that INFO entry not being able to detect your hosting provider.  
Can you share some details on the environment where Filebeat is executing?

Thanks

---

<div class="post-metadata">

**Author:** ![markov](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@markov](https://discuss.elastic.co/u/markov)\
**Post date:** [June 24, 2019, 7:13pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164/3 "2019-06-24T19:13:07Z")

</div>

I am running filebeat on a private network for a company, and logstash in another machine of the network

---

<div class="post-metadata">

**Author:** ![pmercado](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@pmercado](https://discuss.elastic.co/u/pmercado)\
**Post date:** [June 24, 2019, 7:23pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164/4 "2019-06-24T19:23:09Z")

</div>

Is there any error at the logs? I can only see INFO and DEBUG.

Can you share your config files?

Also, can you configure temporarily the console output to make sure that no logs are being gathered?  
[https://www.elastic.co/guide/en/beats/filebeat/current/console-output.html#console-output](https://www.elastic.co/guide/en/beats/filebeat/current/console-output.html#console-output)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 22, 2019, 7:23pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-after-update-add-cloud-metadata-hosting-provider-type-not-detected/187164/5 "2019-07-22T19:23:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.