This happens during startup on all our environments using this Logstash version, regardless of Logstash configuration. I'm speculating that between 7.17.6 (which did not have this behavior) and 7.17.7 ...