# Autodiscovery hints in docker swarm

**URL:** https://discuss.elastic.co/t/autodiscovery-hints-in-docker-swarm/172664
**Category:** Beats
**Created:** [March 17, 2019, 9:36am UTC](https://discuss.elastic.co/t/autodiscovery-hints-in-docker-swarm/172664 "2019-03-17T09:36:53Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![atmosx](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atmosx/32/42183_2.png) [@atmosx](https://discuss.elastic.co/u/atmosx)
#### Post date: [March 17, 2019, 2:18pm UTC](https://discuss.elastic.co/t/autodiscovery-hints-in-docker-swarm/172664/2 "2019-03-17T14:18:32Z")

</div>

I believe the following answer resolves it: [How to use Metricbeat to monitor Docker Swarm containers, hosts and external services](https://discuss.elastic.co/t/how-to-use-metricbeat-to-monitor-docker-swarm-containers-hosts-and-external-services/160037)

The accepted solution is to run metricsbeat in global mode with a set of paths as mounted volumes: [https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-docker.html#\_volume\_mounted\_configuration](https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-docker.html#_volume_mounted_configuration)

---

_[View the full topic](https://discuss.elastic.co/t/autodiscovery-hints-in-docker-swarm/172664)._