Critical application errors should be logged at ERROR level not INFO

Products

• DX Application Performance Management

Issue/Introduction

The following entries were written to the IntroscopeAgent.log file by the kafka-broker-deb8cfbcxt57-24.9.1.25 APMIA extension.

[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output][2025-09-05 22:04:31,143] INFO [ZooKeeperClient Kafka server] Connected. (kafka.zookeeper.ZooKeeperClient)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output][2025-09-05 22:04:31,305] INFO Cluster ID = <id> (kafka.server.KafkaServer)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output][2025-09-05 22:04:31,314] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output]java.lang.RuntimeException: Invalid cluster.id in: /CA_APM/DX/kafka-logs/meta.properties. Expected fnTt_WSZRMGSZcSKXQxl6Q, but read 4e4Xd50wSI6g2v5fqzqrLQ
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output]       at org.apache.kafka.metadata.properties.MetaPropertiesEnsemble.verify(MetaPropertiesEnsemble.java:516)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output]       at kafka.server.KafkaServer.startup(KafkaServer.scala:250)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output]       at kafka.Kafka$.main(Kafka.scala:112)
[INFO] [IntroscopeAgent.KafkaBroker] ProcessStreamPool--2 -> [Kafka Start Output]       at kafka.Kafka.main(Kafka.scala)

This is a problem because production systems typically user WARN or ERROR logging level. Also automated log scanner filtering rules could miss these critical entries.

Resolution

ER DE646655 created