If you are using the bundled JDK then that is probably a bug. Otherwise it is just how things work. logstash wants to collect information about the garbage collector, since it is useful performance information, but it does not know about every GC algorithm. For example, if I add
17:-XX:+UseShenandoahGC
to /etc/logstash/jvm.options then the JVM will run Shenandoah, but logstash will log
[2023-08-04T10:35:40,026][ERROR][logstash.instrument.periodicpoller.jvm] Unknown garbage collector name {:name=>"Shenandoah Pauses"}
[2023-08-04T10:35:40,028][ERROR][logstash.instrument.periodicpoller.jvm] Unknown garbage collector name {:name=>"Shenandoah Cycles"}
every five seconds. It just is. curl -XGET 'localhost:9600/_node/jvm?pretty' works just fine. Not sure if stack monitoring includes detailed GC information anywhere. If it does then it will probably be missing.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.