# Monitoring for logstash 6.3 cannot be used **URL:** \ **Category:** Logstash\ **Created:** [June 27, 2018, 10:29am UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597 "2018-06-27T10:29:59Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![BallGhost](https://avatars.discourse-cdn.com/v4/letter/b/96bed5/32.png) [@BallGhost](https://discuss.elastic.co/u/BallGhost)\ **Post date:** [June 27, 2018, 10:29am UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/1 "2018-06-27T10:29:59Z")
Recently I upgraded to ELK6.3 from 6.2.2，but the monitoring for logstash could not be displayed on kibana. The monitoring for ES and kibana is normal. Here is the logstash.yml """ ... xpack.monitoring.enabled: true xpack.monitoring.elasticsearch.username: \*\*\* xpack.monitoring.elasticsearch.password: \*\*\* xpack.monitoring.elasticsearch.url: \*\*\* ... """ Below is the logstash's error level log [ERROR][logstash.pipeline] Error registering plugin {:pipeline\_id=\>".monitoring-logstash", :plugin=\>"#LogStash::OutputDelegator:0x7592752c", :error=\>"Unrecognized SSL message , plaintext connection?", :thread=\>"#\"} [ERROR][logstash.pipeline] Pipeline aborted due to error {:pipeline\_id=\>".monitoring-logstash", :exception=\>#\, :backtrace=\>["/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/manticore-0.6.1-java/lib/manticore/response.rb:37:in `block in initialize'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/manticore-0.6.1-java/lib/manticore/response.rb:79:in`call'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client/manticore\_adapter.rb:74:in `perform_request'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:291:in`perform\_request\_to\_url'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:245:in `block in healthcheck!'", "org/jruby/RubyHash.java:1343:in`each'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:241:in `healthcheck!'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:341:in`update\_urls'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:71:in `start'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http_client.rb:299:in`build\_pool'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client.rb:63:in `initialize'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:102:in`create\_http\_client'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http\_client\_builder.rb:98:in `build'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch.rb:231:in`build\_client'", "/usr/local/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:24:in `register'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:97:in`register'", "org/logstash/config/ir/compiler/OutputDelegatorExt.java:93:in `register'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:340:in`register\_plugin'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:351:in `block in register_plugins'", "org/jruby/RubyArray.java:1734:in`each'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:351:in `register_plugins'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:728:in`maybe\_setup\_out\_plugins'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:361:in `start_workers'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:288:in`run'", "/usr/local/logstash/logstash-core/lib/logstash/pipeline.rb:248:in `block in start'"], :thread=\>"#\"} [2018-06-27T14:56:28,899][ERROR][logstash.agent] Failed to execute action {:id=\>:".monitoring-logstash", :action\_type=\>LogStash::ConvergeResult::FailedAction, :message=\>"Could not execute action: PipelineAction::Create\<.monitoring-logstash\>, action\_result: false", :backtrace=\>nil} In addition, the index like .monitoring-logstash\* does not exist, and I am using the base license Please help me, Thanks ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [June 27, 2018, 11:04am UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/2 "2018-06-27T11:04:14Z")
Looks like TLS is enabled for the HTTP layer in Elasticsearch but Logstash is attempting to connect over plain http. - > [@BallGhost](#): > > xpack.monitoring.elasticsearch.url: \*\*\* Is that an http URL ? - Is TLS enabled in Elasticsearch for the http layer ? ( you can share the relevant part of your `elasticsearch.yml` ) ---
**Author:** ![BallGhost](https://avatars.discourse-cdn.com/v4/letter/b/96bed5/32.png) [@BallGhost](https://discuss.elastic.co/u/BallGhost)\ **Post date:** [June 27, 2018, 11:23am UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/3 "2018-06-27T11:23:16Z")
As you said, “xpack.monitoring.elasticsearch.url” is https://\*\*\* I just changed it to http, now the monitoring for logstash works properly ,and the error log is gone. Thank you !! ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [June 27, 2018, 11:26am UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/4 "2018-06-27T11:26:26Z")
Glad to hear. I actually misread the error message so : > [@ikakavas](#): > > Looks like TLS is enabled for the HTTP layer in Elasticsearch but Logstash is attempting to connect over plain http. should have been > Looks like TLS is not enabled for the HTTP layer in Elasticsearch but Logstash is attempting to connect over https. ---
**Author:** ![BallGhost](https://avatars.discourse-cdn.com/v4/letter/b/96bed5/32.png) [@BallGhost](https://discuss.elastic.co/u/BallGhost)\ **Post date:** [June 27, 2018, 12:14pm UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/5 "2018-06-27T12:14:50Z")
Haha, this is a small qustion. Thanks again ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 25, 2018, 12:14pm UTC](https://discuss.elastic.co/t/monitoring-for-logstash-6-3-cannot-be-used/137597/6 "2018-07-25T12:14:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.