# Logstash Monitoring is Disabled when i Edit Pipeline settings **URL:** \ **Category:** Logstash\ **Tags:** elastic-stack-monitoring\ **Created:** [May 18, 2020, 12:04pm UTC](https://discuss.elastic.co/t/logstash-monitoring-is-disabled-when-i-edit-pipeline-settings/233101 "2020-05-18T12:04:35Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Rohit\_Kumbhar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohit_kumbhar/32/67682_2.png) [@Rohit\_Kumbhar](https://discuss.elastic.co/u/Rohit_Kumbhar)\ **Post date:** [May 18, 2020, 12:04pm UTC](https://discuss.elastic.co/t/logstash-monitoring-is-disabled-when-i-edit-pipeline-settings/233101/1 "2020-05-18T12:04:35Z")
Hey, I edited Logstash,yml file to increase worker for main Pipeline in result i could not see LOGSTASH MODULE in Stack Monitoring in Kibana Here is my logstash.yml file ``` # ------------ Pipeline Settings -------------- # # The ID of the pipeline. # pipeline.id: main # # Set the number of workers that will, in parallel, execute the filters+outputs # stage of the pipeline. # # This defaults to the number of the host's CPU cores. # pipeline.workers: 4 # # How many events to retrieve from inputs before sending to filters+workers # pipeline.batch.size: 125 # # How long to wait in milliseconds while polling for the next event # before dispatching an undersized batch to filters+outputs # pipeline.batch.delay: 50 # # Force Logstash to exit during shutdown even if there are still inflight # events in memory. By default, logstash will refuse to quit until all # received events have been pushed to the outputs. # # WARNING: enabling this can lead to data loss during shutdown # # pipeline.unsafe_shutdown: false # # ------------ Pipeline Configuration Settings -------------- # # Where to fetch the pipeline configuration for the main pipeline # # path.config: # # Pipeline configuration string for the main pipeline # # config.string: # # At startup, test if the configuration is valid and exit (dry run) # # config.test_and_exit: false # # Periodically check if the configuration has changed and reload the pipeline # This can also be triggered manually through the SIGHUP signal # # config.reload.automatic: false # # How often to check if the pipeline configuration has changed (in seconds) # # config.reload.interval: 3s # # Show fully compiled configuration as debug log message # NOTE: --log.level must be 'debug' # # config.debug: false # # When enabled, process escaped characters such as \n and \" in strings in the # pipeline configuration files. # # config.support_escapes: false # # ------------ Module Settings --------------- # Define modules here. Modules definitions must be defined as an array. # The simple way to see this is to prepend each `name` with a `-`, and keep # all associated variables under the `name` they are associated with, and # above the next, like this: # # modules: # - name: MODULE_NAME # var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE # var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE # var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE # var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE # # X-Pack Monitoring # https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html xpack.monitoring.enabled: true xpack.monitoring.elasticsearch.hosts: ["https://IP:9200", "https://IP2:9200", "https://IP3:9200"] xpack.monitoring.elasticsearch.username: elastic #logstash_system #elastic xpack.monitoring.elasticsearch.password: elastic #xpack.monitoring.elasticsearch.hosts: ["https://es1:9200", "https://es2:9200"] # an alternative to hosts + username/password settings is to use cloud_id/cloud_auth #xpack.monitoring.elasticsearch.cloud_id: monitoring_cluster_id:xxxxxxxxxx #xpack.monitoring.elasticsearch.cloud_auth: logstash_system:password xpack.monitoring.elasticsearch.ssl.certificate_authority: "/home/elk-certificate/ca/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: true #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 #xpack.management.enabled: true #xpack.management.pipeline.id: ["main", "apache_logs"] #xpack.management.elasticsearch.username: elastic #logstash_admin_user #xpack.management.elasticsearch.password: elastic #xpack.management.elasticsearch.hosts: ["https://IP:9200", "https://IP:9200", "https://IP:9200"] # an alternative to hosts + username/password settings is to use cloud_id/cloud_auth #xpack.management.elasticsearch.cloud_id: management_cluster_id:xxxxxxxxxx #xpack.management.elasticsearch.cloud_auth: logstash_admin_user:password #xpack.management.elasticsearch.ssl.certificate_authority: ["/home/elk-certificate/ca/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: true #xpack.management.logstash.poll_interval: 5s ``` Please provide Solution Thanks in Advance ---
**Author:** ![Rohit\_Kumbhar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohit_kumbhar/32/67682_2.png) [@Rohit\_Kumbhar](https://discuss.elastic.co/u/Rohit_Kumbhar)\ **Post date:** [May 18, 2020, 5:28pm UTC](https://discuss.elastic.co/t/logstash-monitoring-is-disabled-when-i-edit-pipeline-settings/233101/2 "2020-05-18T17:28:42Z")
@Badger @shaunak Please Reply ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 18, 2020, 10:21pm UTC](https://discuss.elastic.co/t/logstash-monitoring-is-disabled-when-i-edit-pipeline-settings/233101/3 "2020-05-18T22:21:12Z")
Please don't ping people that are not already part of your topic like that. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 15, 2020, 10:21pm UTC](https://discuss.elastic.co/t/logstash-monitoring-is-disabled-when-i-edit-pipeline-settings/233101/4 "2020-06-15T22:21:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.