# Stack Monitoring: Missing Logstash Pipeline Stats

**URL:** <https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958>\
**Category:** Kibana\
**Created:** [March 10, 2020, 2:28pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958 "2020-03-10T14:28:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomx1](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tomx1](https://discuss.elastic.co/u/tomx1)\
**Post date:** [March 10, 2020, 2:28pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/1 "2020-03-10T14:28:12Z")

</div>

We have a 10 Node Elasticsearch cluster and one single node "cluster" to store all metrics. Those metrics are collected by metricbeat. We ship data into this cluster mainly with logstash. Logstash stats are also gathered by an dedicated metricbeat instance. To view all those metrics we use the Stack Monitoring App in Kibana. This works fine, except for the pipeline stats of logstash. Unfortunately only an empty page is shown if clicking on one of the active pipelines:

 ![Screenshot_2020-03-10 Stack Monitoring - nicat_operations - Logstash - syslogng-vie - Pipelines - Kibana(1)](https://us1.discourse-cdn.com/elastic/original/3X/d/b/db5b5481e5ffe0c58f3a93b5d8157346e2caf8fb.png)

 ![Screenshot_2020-03-10 Stack Monitoring - Logstash - Pipeline - Kibana](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1ec2f22911b6a5251182f0aa1b0224f4549941cc.png)

Security is enabled on both Clusters. If i directly search on the monitoring node via curl then i see all the pipeline stats data  
`curl -k -u user:password https://localhost:9200/.monitoring-logstash-7-mb-2020.03.10/_search?pretty`

Any Idea what the problem could be?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [March 13, 2020, 5:34am UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/2 "2020-03-13T05:34:10Z")

</div>

On what version of the stack are you on? There were some known issues on 7.3.0 :Please refer here if you are on that version: [https://github.com/elastic/support-known-issues/issues/1](https://github.com/elastic/support-known-issues/issues/1)

cc @chrisronline

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![tomx1](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tomx1](https://discuss.elastic.co/u/tomx1)\
**Post date:** [March 13, 2020, 7:13am UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/3 "2020-03-13T07:13:38Z")

</div>

Hi rashmi... we are currently on 7.6.0

---

<div class="post-metadata">

**Author:** ![Igor\_Zaytsev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_zaytsev/32/50662_2.png) [@Igor\_Zaytsev](https://discuss.elastic.co/u/Igor_Zaytsev)\
**Post date:** [March 13, 2020, 5:03pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/4 "2020-03-13T17:03:13Z")

</div>

@tomx1 I don’t think this is a security issue, since everything else seems to be working fine. We do however have an issue where if you explicitly set `enable_metric` to false the pipeline page will be empty: [https://github.com/elastic/kibana/issues/44626](https://github.com/elastic/kibana/issues/44626) which happens in version 6.8 and above.

Are you seeing any errors in the browser's console? Or, any warnings/errors in ES, LS, and KB consoles?

---

<div class="post-metadata">

**Author:** ![tomx1](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tomx1](https://discuss.elastic.co/u/tomx1)\
**Post date:** [March 18, 2020, 10:21am UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/5 "2020-03-18T10:21:48Z")

</div>

I don't use the enable\_metric option but yes, I see the following errors in the browser console (chrome):

```
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-P5polb1UreUSOe5V/Pv7tc+yeZuJXiOi/3fqhGsU7BE='), or a nonce ('nonce-...') is required to enable inline execution.

bootstrap.js:9 ^ A single error about an inline script not firing due to content security policy is expected!
vendors_1.bundle.dll.js:113 INFO: 2020-03-18T15:15:53Z
  Adding connection to https://example.com/elasticsearch

kbn-ui-shared-deps.js:368 TypeError: Cannot read property 'graph' of undefined
    at Config.update (monitoring.bundle.js:3)
    at PipelineState.update (monitoring.bundle.js:3)
    at new PipelineState (monitoring.bundle.js:3)
    at monitoring.bundle.js:3
    at u.$digest (kbn-ui-shared-deps.js:368)
    at u.$apply (kbn-ui-shared-deps.js:368)
    at monitoring.bundle.js:3
```

---

<div class="post-metadata">

**Author:** ![Igor\_Zaytsev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_zaytsev/32/50662_2.png) [@Igor\_Zaytsev](https://discuss.elastic.co/u/Igor_Zaytsev)\
**Post date:** [March 18, 2020, 12:12pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/6 "2020-03-18T12:12:13Z")

</div>

This might be a result of a known issue with long running queries noted here: [https://github.com/elastic/kibana/issues/57327](https://github.com/elastic/kibana/issues/57327)

Can you please try one of the following:

- Increase (or decrease) the time range at the top right
- Increasing `elasticsearch.requestTimeout` setting in your kibana.yml file

Let me know if any of these work

---

<div class="post-metadata">

**Author:** ![tomx1](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tomx1](https://discuss.elastic.co/u/tomx1)\
**Post date:** [March 18, 2020, 3:20pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/7 "2020-03-18T15:20:14Z")

</div>

Unfortunately no success. I've increased request timeout to 60000 and tried several time ranges.

---

<div class="post-metadata">

**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\
**Post date:** [March 20, 2020, 3:34pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/8 "2020-03-20T15:34:23Z")

</div>

Hi @tomx1,

Can you run this query against the monitoring cluster and return the results?

```auto
POST .monitoring-logstash-*/_search?filter_path=hits.hits._source.logstash_state
{
  "size": 1,
  "sort": {
    "timestamp": {
      "order": "desc"
    }
  },
  "query": {
    "bool": {
      "filter": [
        {
          "term": {
            "type": "logstash_state"
          }
        }
      ]
    }
  }
}

```

---

<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:** [April 17, 2020, 3:36pm UTC](https://discuss.elastic.co/t/stack-monitoring-missing-logstash-pipeline-stats/222958/9 "2020-04-17T15:36:13Z")

</div>

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