ParNew and ConcurrentMarkSweep seen in logs

Elastic Stack Logstash
1

Good Afternoon everyone;

I am seeing the following lines when I place my Logstash in Debug mode to collect logs. I have a feeling that it is what is stopping me from seeing any syslog that has been forwarded to the logstash.

system.syslog
[2021-11-09T13:05:46,805][DEBUG][logstash.outputs.file ][main] Starting flush cycle
13:05:46.000
system.syslog
[2021-11-09T13:05:46,950][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
13:05:46.000
system.syslog
[2021-11-09T13:05:46,950][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
13:05:46.805
logstash.log
[logstash.log][DEBUG] Starting flush cycle
13:05:46.950
logstash.log
[logstash.log][DEBUG] collector name {:name=>"ParNew"}
13:05:46.950
logstash.log
[logstash.log][DEBUG] collector name {:name=>"ConcurrentMarkSweep"}
13:05:48.000
system.syslog
[2021-11-09T13:05:48,806][DEBUG][logstash.outputs.file ][main] Starting flush cycle
13:05:48.806
logstash.log
[logstash.log][DEBUG] Starting flush cycle
13:05:49.000
system.syslog
[2021-11-09T13:05:49,687][DEBUG][org.logstash.execution.PeriodicFlush][main] Pushing flush onto pipeline.

If this is bad, what steps would I take to remove it?
Thank you for your assistance.

2

This is normal. Personally I would prefer most of those message be TRACE rather than DEBUG.

3

Thank you Badger for the input. So seeing multiple "ParNew" and "ConcurrentMarkSweep" lines per minute is normal and should not be worrisome?

4

That is correct.

5

Thank you. We can close this question then.

6

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