JMX Logging

JMX logs contain information about JMX interactions between Splunk AppDynamics agents and the monitored server's JMX domains.

JMX log entries are useful for diagnosing problems associated with JMX metrics or with JVM metrics that rely on JMX. For example, they can help you determine why MBeans or metrics created from MBeans do not appear in the Controller UI.

The name of the log is JMXYear_mon_day_hr_min.#.log, where # is the log set. See Agent Log Files for information about the structure of the log files into sets.

The JMX log file can reach a maximum of 5MB within a set.

Collecting JMX log (sample):

<ADRRAFAppender name="JMXLogger" fileName="JMX.log">
            <PatternLayout pattern="[%t] %d{DATE} %5p - %m%n" />
            <SizeBasedTriggeringPolicy size="20 MB" />
            <ADRolloverStrategy max="5" />
        </ADRRAFAppender>

<AsyncLogger name="com.singularity.JMX" level="info" additivity="false">
            <AppenderRef ref="JMXLogger" />
        </AsyncLogger>

These configurations can be used in log4j2.xml file.