# Problem adding Logstash to Kibana monitoring **URL:** \ **Category:** Logstash\ **Tags:** elastic-stack-monitoring\ **Created:** [November 21, 2018, 7:34am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638 "2018-11-21T07:34:59Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [November 21, 2018, 7:34am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/1 "2018-11-21T07:34:59Z")
Hi All, I have a problem to add Logstash monitoring to Kibana. I have followed the configuration guidelines, but the Logstash widget does not appear on Kibana Monitoring tab. My logstash.yml: node.name: node-1 path.data: /var/lib/logstash path.logs: /var/log/logstash # X-Pack Monitoring # [https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html](https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html) xpack.monitoring.enabled: true xpack.monitoring.elasticsearch.username: logstash\_system xpack.monitoring.elasticsearch.password: password #xpack.monitoring.elasticsearch.url: ["[http://192.168.16.124:9200](http://192.168.16.124:9200)"] #xpack.monitoring.elasticsearch.ssl.ca: ["/path/to/ca.crt"] #xpack.monitoring.elasticsearch.ssl.truststore.path: path/to/file #xpack.monitoring.elasticsearch.ssl.truststore.password: password #xpack.monitoring.elasticsearch.ssl.keystore.path: /path/to/file #xpack.monitoring.elasticsearch.ssl.keystore.password: password #xpack.monitoring.elasticsearch.ssl.verification\_mode: certificate #xpack.monitoring.elasticsearch.sniffing: false #xpack.monitoring.collection.interval: 10s #xpack.monitoring.collection.pipeline.details.enabled: true # # X-Pack Management # [https://www.elastic.co/guide/en/logstash/current/logstash-centralized-pipeline-management.html](https://www.elastic.co/guide/en/logstash/current/logstash-centralized-pipeline-management.html) #xpack.management.enabled: true #xpack.management.pipeline.id: ["main", "apache\_logs"] #xpack.management.elasticsearch.username: elastic #xpack.management.elasticsearch.password: password #xpack.management.elasticsearch.url: ["[http://192.168.16.124:9200](http://192.168.16.124:9200)"] #xpack.management.elasticsearch.ssl.ca: ["/path/to/ca.crt"] #xpack.management.elasticsearch.ssl.truststore.path: /path/to/file #xpack.management.elasticsearch.ssl.truststore.password: password #xpack.management.elasticsearch.ssl.keystore.path: /path/to/file #xpack.management.elasticsearch.ssl.keystore.password: password #xpack.management.elasticsearch.ssl.verification\_mode: certificate #xpack.management.elasticsearch.sniffing: false #xpack.management.logstash.poll\_interval: 5s ES and Kibana appears on the Kibana"s Monoitoring tab, but Logstash does not. Have you got any idea what have I missed? Thanks! ---
**Author:** ![aravindputrevu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aravindputrevu/32/24816_2.png) [@aravindputrevu](https://discuss.elastic.co/u/aravindputrevu)\ **Post date:** [November 21, 2018, 7:44am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/2 "2018-11-21T07:44:50Z")
May I know which version of Elasticsearch, Kibana and Logstash you are using? Also, just in case, if you haven't seen these are the instructions to [configure logstash monitoring for latest version 6.5](https://www.elastic.co/guide/en/logstash/current/configuring-logstash.html) ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [November 21, 2018, 7:58am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/3 "2018-11-21T07:58:47Z")
Sorry, I did not mentioned the version - it is 6.4.1 (all of the products). I have followed that instruction, but the expected result was not reached. ---
**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:** [November 21, 2018, 2:16pm UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/4 "2018-11-21T14:16:16Z")
What is your cluster setup like? Do you have a single cluster for everything, or do you have a dedicated monitoring cluster? ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [November 22, 2018, 5:38am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/5 "2018-11-22T05:38:48Z")
It is a development site, so single cluster for everything. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [November 22, 2018, 9:17am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/6 "2018-11-22T09:17:34Z")
Could you restart Logstash and post the first 50 lines of logs? I want to see if there are any errors or other messages related to Monitoring. Thanks. ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [November 22, 2018, 12:54pm UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/7 "2018-11-22T12:54:23Z")
Hi, Please find it below: [2018-11-22T13:48:57,699][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.4.1"} [2018-11-22T13:48:57,964][INFO][logstash.config.source.local.configpathloader] No config files found in path {:path=\>"/etc/logstash/conf.d/_.conf"} [2018-11-22T13:49:01,725][WARN][logstash.outputs.elasticsearch] You are using a deprecated config setting "document\_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=\>"document\_type", :plugin=\>\"/\_xpack/monitoring/\_bulk?system\_id=logstash&system\_api\_version=2&interval=1s", password=\>, hosts=\>[[http://localhost:9200](http://localhost:9200)], sniffing=\>false, manage\_template=\>false, id=\>"2a5bb8c07e5addf47bc222c03efa114ade32f5cbb3114ae9a3443541240db08e", user=\>"logstash\_system", document\_type=\>"%{[@metadata][document\_type]}", enable\_metric=\>true, codec=\>\"plain\_dbb705e1-636d-40a6-84f9-cbcc21e9c46a", enable\_metric=\>true, charset=\>"UTF-8"\>, workers=\>1, template\_name=\>"logstash", template\_overwrite=\>false, doc\_as\_upsert=\>false, script\_type=\>"inline", script\_lang=\>"painless", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_initial\_interval=\>2, retry\_max\_interval=\>64, retry\_on\_conflict=\>1, action=\>"index", ssl\_certificate\_verification=\>true, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false\>} [2018-11-22T13:49:01,914][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>".monitoring-logstash", "pipeline.workers"=\>1, "pipeline.batch.size"=\>2, "pipeline.batch.delay"=\>50} [2018-11-22T13:49:03,245][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[], :added=\>[[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)]}} [2018-11-22T13:49:03,285][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/), :path=\>"/"} [2018-11-22T13:49:04,025][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)"} [2018-11-22T13:49:04,144][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es\_version=\>6} [2018-11-22T13:49:04,153][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} [2018-11-22T13:49:04,281][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::ElasticSearch", :hosts=\>["[http://localhost:9200](http://localhost:9200)"]} [2018-11-22T13:49:04,536][INFO][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[], :added=\>[[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)]}} [2018-11-22T13:49:04,540][INFO][logstash.licensechecker.licensereader] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/), :path=\>"/"} [2018-11-22T13:49:04,555][WARN][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=\>"[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)"} [2018-11-22T13:49:04,563][INFO][logstash.licensechecker.licensereader] ES Output version determined {:es\_version=\>6} [2018-11-22T13:49:04,564][WARN][logstash.licensechecker.licensereader] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} [2018-11-22T13:49:04,868][INFO][logstash.pipeline] Pipeline started successfully {:pipeline\_id=\>".monitoring-logstash", :thread=\>"#\"} [2018-11-22T13:49:04,989][INFO][logstash.agent] Pipelines running {:count=\>1, :running\_pipelines=\>[:".monitoring-logstash"], :non\_running\_pipelines=\>[]} [2018-11-22T13:49:05,025][INFO][logstash.inputs.metrics] Monitoring License OK [2018-11-22T13:49:05,620][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600} [2018-11-22T13:49:11,268][INFO][logstash.pipeline] Pipeline has terminated {:pipeline\_id=\>".monitoring-logstash", :thread=\>"#\"} [2018-11-22T13:50:01,356][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.4.1"} [2018-11-22T13:50:01,750][INFO][logstash.config.source.local.configpathloader] No config files found in path {:path=\>"/etc/logstash/conf.d/_.conf"} [2018-11-22T13:50:06,549][WARN][logstash.outputs.elasticsearch] You are using a deprecated config setting "document\_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=\>"document\_type", :plugin=\>\"/\_xpack/monitoring/\_bulk?system\_id=logstash&system\_api\_version=2&interval=1s", password=\>, hosts=\>[[http://localhost:9200](http://localhost:9200)], sniffing=\>false, manage\_template=\>false, id=\>"2a5bb8c07e5addf47bc222c03efa114ade32f5cbb3114ae9a3443541240db08e", user=\>"logstash\_system", document\_type=\>"%{[@metadata][document\_type]}", enable\_metric=\>true, codec=\>\"plain\_5b891dff-8af6-47e5-8a3d-6aec2639472d", enable\_metric=\>true, charset=\>"UTF-8"\>, workers=\>1, template\_name=\>"logstash", template\_overwrite=\>false, doc\_as\_upsert=\>false, script\_type=\>"inline", script\_lang=\>"painless", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_initial\_interval=\>2, retry\_max\_interval=\>64, retry\_on\_conflict=\>1, action=\>"index", ssl\_certificate\_verification=\>true, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false\>} [2018-11-22T13:50:06,716][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>".monitoring-logstash", "pipeline.workers"=\>1, "pipeline.batch.size"=\>2, "pipeline.batch.delay"=\>50} [2018-11-22T13:50:07,677][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)]}} [2018-11-22T13:50:07,721][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/), :path=\>"/"} [2018-11-22T13:50:08,276][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://logstash\_system:xxxxxx@localhost:9200/](http://logstash_system:xxxxxx@localhost:9200/)"} Thanks, P. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [November 22, 2018, 5:20pm UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/8 "2018-11-22T17:20:48Z")
Thanks for the log. I don't see anything abnormal there. Next, while your Logstash node is running, could you run `curl -v http://localhost:9600/_node/pipelines` from the same machine and post the results here? ---
**Author:** ![pszemesy](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@pszemesy](https://discuss.elastic.co/u/pszemesy)\ **Post date:** [November 23, 2018, 8:51am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/9 "2018-11-23T08:51:16Z")
Hi, I have checked it the connection is refused. I have checked the opened ports on the server and logstash does not opened any ports - although the port opening was ment to be successful in the log. `[2018-11-22T13:49:05,620][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=>9600}` My colleague mentioned I may have to use JAVA setcap in order to open the port - but port 9600 is not privileged as far as I know?! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 21, 2018, 8:51am UTC](https://discuss.elastic.co/t/problem-adding-logstash-to-kibana-monitoring/157638/10 "2018-12-21T08:51:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.