Logstash.instrument.periodicpoller.jvm purpose / how to disable via logstash settings?

bgeels · May 6, 2019, 11:02pm

Hi All,

I'm trying to diagnose where time is going starting up my logstash instance. I have multiple pipelines with many filters in each.

Watching the debug logs I see many statements like the below ( I'm not positive but it seem like it's likely one per plugin). It seems like these are just metric collectors for use via the API to perform some introspection? ( I may be wrong ).

I'm also guessing that this may disable creating them?

github.com

elastic/logstash/blob/master/logstash-core/lib/logstash/environment.rb#L37


                 Setting.new("modules_list", Array, []),
                 Setting.new("modules_variable_list", Array, []),
        Setting::Modules.new("cloud.id", LogStash::Util::CloudSettingId),
        Setting::Modules.new("cloud.auth",LogStash::Util::CloudSettingAuth),
        Setting::Boolean.new("modules_setup", false),
        Setting::Boolean.new("config.test_and_exit", false),
        Setting::Boolean.new("config.reload.automatic", false),
        Setting::TimeValue.new("config.reload.interval", "3s"), # in seconds
        Setting::Boolean.new("config.support_escapes", false),
         Setting::String.new("config.field_reference.parser", "STRICT", true, %w(STRICT)),
        Setting::Boolean.new("metric.collect", true),
         Setting::String.new("pipeline.id", "main"),
        Setting::Boolean.new("pipeline.system", false),
Setting::PositiveInteger.new("pipeline.workers", LogStash::Config::CpuCoreStrategy.maximum),
Setting::PositiveInteger.new("pipeline.batch.size", 125),
        Setting::Numeric.new("pipeline.batch.delay", 50), # in milliseconds
        Setting::Boolean.new("pipeline.unsafe_shutdown", false),
        Setting::Boolean.new("pipeline.java_execution", true),
        Setting::Boolean.new("pipeline.reloadable", true),
        Setting::Boolean.new("pipeline.plugin_classloaders", false),
                 Setting.new("path.plugins", Array, []),

I've tried setting:
metric.collect: false
to no avail in /etc/logstash/logstash.yml. ( After setting that and restarting logstash I still see the below in the logs ).

Any help would be greatly appreciated. Thanks!

[2019-05-06T22:45:01,289][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:01,290][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}
[2019-05-06T22:45:06,296][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:06,297][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}
[2019-05-06T22:45:11,304][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:11,304][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}
[2019-05-06T22:45:16,311][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:16,312][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}
[2019-05-06T22:45:21,319][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:21,320][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}
[2019-05-06T22:45:26,381][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Young Generation"}
[2019-05-06T22:45:26,382][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"G1 Old Generation"}

system · June 3, 2019, 11:06pm

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