SLF4J Error with Wildfly 31.0.1.Final Client JAR

[kmix]

When referencing the Wildfly 31.0.1.Final jboss-cli-client.jar as a custom_jar_paths property, I'm seeing the following error in the jmxfetch.log:

2024-03-11 14:35:04 MDT | JMX | INFO | Reporter | Instance jboss_wildfly is sending 89 metrics to the metrics reporter during collection #10210
2024-03-11 14:36:04 MDT | JMX | INFO | JmxFetch | JMXFetch is closing
SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J(W): Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J(W): Ignoring binding found at [jar:file:/opt/datadog-agent/bin/agent/dist/jmx/jmxfetch.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J(W): See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.

After this error, no other logging happens until the agent is restarted. When I fall back to a Wildfly 26.1.3.Final client JAR, the jmxfetch.log populates as expected.

Wildfly Integration Guide:
https://docs.datadoghq.com/integrations/java/?tab=host#monitoring-jboss-wildfly-applications

Sample Integration Configuration:
https://github.com/DataDog/integrations-core/blob/master/jboss_wildfly/datadog_checks/jboss_wildfly/data/conf.yaml.example#L51

[carlosroman]

@kmix Which version of the Agent are you using?

[kmix]

This was tested on servers running 7.51.0 & 7.51.1.

[carlosroman]

Looks like 31.0.1.Final comes with slf4j-api-2.0.11 while 26.1.3.Final comes with slf4j-api-1.7.36. That would explain the error you see. As we have to target Java 7 we can not move to using SLF4J 2.0.x as that requires a Java 8. Not sure there is a work around for this as removing SLF4J from Wildfly client might break things and same with removing/replacing it in JMXFetch. I'll see what can be done.