# X-Pack monitoring shows one of all of the configured Logstash nodes
**URL:** https://discuss.elastic.co/t/x-pack-monitoring-shows-one-of-all-of-the-configured-logstash-nodes/142760
**Category:** Logstash
**Created:** [August 2, 2018, 12:16pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-shows-one-of-all-of-the-configured-logstash-nodes/142760 "2018-08-02T12:16:53Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@aaber](https://discuss.elastic.co/u/aaber)
#### Post date: [August 2, 2018, 12:16pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-shows-one-of-all-of-the-configured-logstash-nodes/142760/1 "2018-08-02T12:16:53Z")
When you configure X-Pack to monitor multiple Logstash instances make sure each instance has a unique uuid.
We copied AMIs in AWS to create multiple Logstash instances and all of the instances had the same uuid which confused the X-Pack monitoring server.
# Change the uuid of a Logstash server:
1. $ sudo -i
2. # uuidgen \> /var/lib/logstash/uuid
3. # tr -d "\n\r" \< /var/lib/logstash/uuid \> tempo ; mv tempo /var/lib/logstash/uuid
4. # service logstash restart
Enjoy.
---
### Author:  [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [August 10, 2018, 2:42pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-shows-one-of-all-of-the-configured-logstash-nodes/142760/2 "2018-08-10T14:42:39Z")
This is a nice trick. One alternative would be to remove the `uuid` file before creating the AMI. That way each Logstash instance will automatically create the file with a unique UUID upon start up.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 7, 2018, 2:54pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-shows-one-of-all-of-the-configured-logstash-nodes/142760/3 "2018-09-07T14:54:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.