# Logstash and x-pack monitoring

**URL:** <https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929>\
**Category:** Logstash\
**Created:** [July 13, 2017, 5:27am UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929 "2017-07-13T05:27:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jupp](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jupp](https://discuss.elastic.co/u/jupp)\
**Post date:** [July 13, 2017, 5:27am UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/1 "2017-07-13T05:27:12Z")

</div>

hi people, why i can not write my logstash x-pack monitoring data directly in a dedicated monitoring cluster?  
greetz jupp

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 13, 2017, 8:05am UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/2 "2017-07-13T08:05:02Z")

</div>

Can you please invest some time and write a more useful error description? This post does neither contain, what you tried so far, nor what has failed, nor what you expected to work. You have not mentioned the version of the stack that you are using, nor how your configuration on the logstash and elasticsearch side looks like.

---

<div class="post-metadata">

**Author:** ![jupp](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jupp](https://discuss.elastic.co/u/jupp)\
**Post date:** [July 13, 2017, 9:24am UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/3 "2017-07-13T09:24:53Z")

</div>

Hi spinscale,

sorry for my lazy request. I have no error but I am wondering why I have to send my monitoring data to my production-cluster even when I have a dedicated monitoring cluster.

I found this information in the docs:  
[https://www.elastic.co/guide/en/x-pack/current/monitoring-logstash.html](https://www.elastic.co/guide/en/x-pack/current/monitoring-logstash.html)

> Configure your Logstash nodes to send metrics to your production Elasticsearch cluster by setting the xpack.monitoring.elasticsearch.url in logstash.yml. If security is enabled, you also need to specify the credentials for the built-in logstash\_system user.

> Important

> Even if you are using a dedicated monitoring cluster, you must configure your Logstash nodes to send metrics to your production cluster. Metrics cannot be sent directly to the monitoring cluster.

When the production cluster is out of order the logstash monitoring data would be inaccessible. Am I right? Would't it be better to send the monitoring-data directly do the dedicated monitoring cluster. I thought this is one of the main benefits when I have a dedicated monitoring cluster.

---

<div class="post-metadata">

**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\
**Post date:** [July 13, 2017, 1:57pm UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/4 "2017-07-13T13:57:56Z")

</div>

Hey @jupp

You can send your Logstash monitoring data to a dedicated monitoring cluster directly. If you send your Logstash monitoring data to the production cluster, you will see the monitoring data grouped nicely for each cluster. As an example, you may have multiple Elasticsearch clusters and multiple Logstash nodes talking to those clusters, and having a visible group of separation in the monitoring app can help with understanding your setup easily and associate the monitoring data within those groups. All this said, we are improving the wording for clarity and adding some visuals to the linked documentation page, so please stay tuned for that update.

Thanks,  
Bohyun

---

<div class="post-metadata">

**Author:** ![jupp](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jupp](https://discuss.elastic.co/u/jupp)\
**Post date:** [July 13, 2017, 2:29pm UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/5 "2017-07-13T14:29:27Z")

</div>

Hi bohyun,

thank you for clarification 🙂

So I have to decide between Nice Grouping vs. no Monitoring of Logstash when Production-Cluster is gone.  
Am I right?

Greetz Jupp

---

<div class="post-metadata">

**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\
**Post date:** [July 13, 2017, 3:16pm UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/6 "2017-07-13T15:16:43Z")

</div>

Hi @jupp

It can be a bit more involved than that. Sometimes our users may not be able to set up another cluster for various reasons including lack of resources. By having an ability to send your Logstash monitoring data to your production cluster, you are not flying blindly and will have visibility into your Logstash nodes.

Thanks,  
Bohyun

---

<div class="post-metadata">

**Author:** ![jupp](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jupp](https://discuss.elastic.co/u/jupp)\
**Post date:** [July 28, 2017, 6:37pm UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/7 "2017-07-28T18:37:49Z")

</div>

Hi bohuyun,

the Documentation is now clearer. Thank you. 🙂

---

<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:** [August 25, 2017, 6:38pm UTC](https://discuss.elastic.co/t/logstash-and-x-pack-monitoring/92929/8 "2017-08-25T18:38:00Z")

</div>

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