# Configuring Metricbeat to send data to other machine **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [July 11, 2018, 1:43pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583 "2018-07-11T13:43:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jtstorey](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jtstorey](https://discuss.elastic.co/u/jtstorey)\ **Post date:** [July 11, 2018, 1:43pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/1 "2018-07-11T13:43:40Z")
I have two VMs. One of them is running elasticsearch and kibana, the other is running metricbeat. I am trying to get the 2nd VM to send its data to the 1st. I thought that the only configuration was to put the IP of the 1st machine in the metricbeat.yml file. > output.elasticsearch: > hosts:[" **_1stVMIP_** :9200"] This doesn't seem to be getting the data to elasticsearch though. Is there other configuration I need to do? Maybe something on the elasticsearch side to let it accept data from the 2nd VM? ---
**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\ **Post date:** [July 11, 2018, 2:00pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/2 "2018-07-11T14:00:52Z")
It should be enough. Are you sure you can connect to your first VM from your second? E.g. ```auto curl 1stVMIP:9200 ``` ---
**Author:** ![jtstorey](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jtstorey](https://discuss.elastic.co/u/jtstorey)\ **Post date:** [July 11, 2018, 2:04pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/3 "2018-07-11T14:04:53Z")
I am not, but I will look into that. I am quite new to using VMs as well as elasticsearch. ---
**Author:** ![jtstorey](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jtstorey](https://discuss.elastic.co/u/jtstorey)\ **Post date:** [July 12, 2018, 8:09pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/4 "2018-07-12T20:09:24Z")
After some time working on the network configuration between my two VMs, I can now get a response from curl, but the data from metricbeat is still not showing up in Kibana. ---
**Author:** ![jtstorey](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jtstorey](https://discuss.elastic.co/u/jtstorey)\ **Post date:** [July 12, 2018, 8:49pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/5 "2018-07-12T20:49:23Z")
After a bit of additional debugging I have finally gotten it to work. I will provide a summary off what I did incase anyone else has this issue: After configuring the Network between my VMs, ping would work, but curl would not. I found a source online [here](https://www.linuxquestions.org/questions/linux-networking-3/odd-problem-no-route-to-host-put-can-ping-879681/) that said to do "iptables -F" which to my understanding disabled firewalls. At this point I could curl, but data was still not getting into elasticsearch. I checked the metricbeat logs and found a line saying "Ping request failed... server gave HTTP response to HTTPS client" so I re-commented the protocol setting in metricbeat.yml. Also, at some point during my trouble shooting I changed network.host in the elasticsearch.yml file to the IP of the machine. When I tried resetting it to the default of localhost, kibana would say that login was disabled. I do not know why this is the case, but the system is now working with network.host set as the IP. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 9, 2018, 8:49pm UTC](https://discuss.elastic.co/t/configuring-metricbeat-to-send-data-to-other-machine/139583/6 "2018-08-09T20:49:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.