# 8.1.1 Cannot display Logstash pipeline in monitoring UI

**URL:** <https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554>\
**Category:** Kibana\
**Created:** [March 24, 2022, 10:06am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554 "2022-03-24T10:06:28Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 10:06am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/1 "2022-03-24T10:06:28Z")

</div>

I have migrated the Elastic stack from 7.17.1 to 8.1.1. After the upgrade everything works fine, except the Kibana monitoring logstash pipeline viewer UI.

stack monitoring \> logstash \> pipelines

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/c/eceb280def50472e5a5020a5dd2b91cc6aefd850.png)

pipeline main points to [https://fqdn/app/monitoring#/logstash/pipelines/main?\_g=(cluster\_uuid:cluster\_id,refreshInterval:(pause:!f,value:10000),time:(from:now-15m,to:now)](https://fqdn/app/monitoring#/logstash/pipelines/main?_g=(cluster_uuid:cluster_id,refreshInterval:(pause:!f,value:10000),time:(from:now-15m,to:now)))

After clicking on the main pipeline, I get an empty screen.

POST request [https://fqdn/api/monitoring/v1/clusters/cluster\_id/logstash/pipeline/main](https://fqdn/api/monitoring/v1/clusters/cluster_id/logstash/pipeline/main) returns payload

```auto
"pipeline":{"data":null,"isBoom":true,"isServer":false,"output":{"statusCode":404,"payload":{"statusCode":404,"error":"Not Found","message":"Pipeline [main @] not found in the selected time range for cluster [cluster_id]."},"headers":{}}}}

```

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 10:15am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/2 "2022-03-24T10:15:28Z")

</div>

Have you checked you pipelines, for example the ingestion pipelines after running the setup command for the various modules ?

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 12:01pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/3 "2022-03-24T12:01:18Z")

</div>

Hi @zx8086, what can I check? All my Logstash pipeline config files are properly working (tested using `logstash -t -f %s`).

```auto
[2022-03-24T12:58:38,338][INFO][logstash.agent] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}

```

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 12:39pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/4 "2022-03-24T12:39:59Z")

</div>

How are you monitoring ? Metricbeat ? Logstash-xpack module ?

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 1:12pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/5 "2022-03-24T13:12:44Z")

</div>

yes, correct

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 1:16pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/6 "2022-03-24T13:16:30Z")

</div>

Would help to see the Logstash configuration as well as the metricbeat module configuration and logs. Metricbeat logs will show if the modules is working and data being sent not.

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 1:32pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/7 "2022-03-24T13:32:08Z")

</div>

`/etc/logstash/logstash.yml`

```auto
path.logs: /var/log/logstash
http.host: 192.168.1.213
http.port: 9600
pipeline.ecs_compatibility: disabled
xpack.management.enabled: false
monitoring.cluster_uuid: "cluster_id"

```

`/etc/metricbeat/modules.d/logstash-xpack.yml`

```auto
- module: logstash
  xpack.enabled: true
  period: 10s
  hosts: ["http://192.168.1.213:9600"]
  username: "remote_monitoring_user"
  password: "xxxxxxxxx"
  metricsets:
    - node
    - node_stats

```

`grep metricbeat /var/log/syslog`

![image](https://us1.discourse-cdn.com/elastic/original/3X/c/0/c080f4fb9716cb204547712ae4fc06a5b0aef4c6.png)

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 1:54pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/8 "2022-03-24T13:54:55Z")

</div>

Configured this ?

```auto
monitoring.enabled: false

```

Also you can use a curl command to see if the http endpoint is working

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 2:02pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/9 "2022-03-24T14:02:16Z")

</div>

sorry I left out lines below (`/etc/logstash/logstash.yml`)

```auto
# disable internal monitoring; replaced by metricbeat
monitoring.enabled: false

```

```auto
curl http://remote_monitoring_user:xxxxxxx@192.168.1.213:9600

{"host":"xxxxxx","version":"8.1.1","http_address":"192.168.1.213:9600","id":"xxxxxxxxxx","name":"xxxxxxx","ephemeral_id":"xxxxxxxxxx","status":"green","snapshot":false,"pipeline":{"workers":24,"batch_size":125,"batch_delay":50},"monitoring":{"cluster_uuid":"cluster_id"},"build_date":"2022-03-17T22:01:47Z","build_sha":"xxxxxxxxxx","build_snapshot":false}

```

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 2:54pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/10 "2022-03-24T14:54:45Z")

</div>

Do you see the same calls reflected in the metricbeat logs ? Is metricbeat making the call to that same address, same credentials and having the same response ?

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 3:09pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/11 "2022-03-24T15:09:35Z")

</div>

Also what about using the default settings? Metricbeat is running on the same node as logstash right ? So localhost should work too.

````auto
- module: logstash
  xpack.enabled: true
  period: 10s
  hosts: ["localhost:9600"]
  #username: "user"
  #password: "secret"```
````

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 3:24pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/12 "2022-03-24T15:24:14Z")

</div>

localhost does not work as the port is not bound to all interfaces (but only to the IP adres 192.168.1.213)

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 24, 2022, 3:30pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/13 "2022-03-24T15:30:34Z")

</div>

I only see metricbeat log events like `Non-zero metrics in the last 30s` in `/var/log/syslog`.

```auto
..."logstash":{"node_stats":{"events":3,"success":3}}...

```

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 24, 2022, 3:50pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/14 "2022-03-24T15:50:43Z")

</div>

> [@jsteenkamp](#):
>
> ```auto
> metricsets:
> - node
> - node_stats
> 
> ```

And if you remove the metricset ? that might be the problem

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 25, 2022, 8:22am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/15 "2022-03-25T08:22:22Z")

</div>

I have removed the metricsets and restarted the metricbeat service. Same issue. I have restored the config file and restarted the service again.

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [March 25, 2022, 9:36am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/16 "2022-03-25T09:36:21Z")

</div>

The logstash config you shared, was that the full one ? Hard to diagnose the issue on limited information.

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [March 25, 2022, 3:00pm UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/17 "2022-03-25T15:00:02Z")

</div>

yes, I only left out `monitoring.enabled: false`

---

<div class="post-metadata">

**Author:** ![jsteenkamp](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jsteenkamp](https://discuss.elastic.co/u/jsteenkamp)\
**Post date:** [April 4, 2022, 10:54am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/18 "2022-04-04T10:54:29Z")

</div>

This issue appears to be fixed in version 8.1.2

---

<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:** [May 2, 2022, 10:55am UTC](https://discuss.elastic.co/t/8-1-1-cannot-display-logstash-pipeline-in-monitoring-ui/300554/19 "2022-05-02T10:55:07Z")

</div>

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