Splunk AppDynamics

IBM java agen

Ahmedkhalil
Communicator

Dears,

i am checking my agent BytecodeTransfomrer and found all of entries are mentioning 

Matching runtime class : no class match found 

is this normal Logs or there is some issues in my installation 

Labels (1)
0 Karma
1 Solution

Peter_Holditch
Builder

That's perfectly normal.  Tha agent logs the loading of al the classes in your application.  "no class match found" in the ByteCode log simply indicates that no rule was found that requires that the class named in the log entry be instrumented.

ie this:

[AD Thread-BCI Transform Processor0] 11 Jul 2017 10:16:44,785 Matching class name org/springframework/boot/SpringApplication Matching class bytecode. : No class match found.

Indicates that no rule matched the org.springframework.boot.SpringApplication class

You can tell what HAS been instrumented from entries like:

[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching class name ch/qos/logback/core/ConsoleAppender Matching class bytecode. : Class match found.
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method <init> (()V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method setTarget ((Ljava/lang/String;)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method getTarget (()Ljava/lang/String;)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Matching method targetWarn ((Ljava/lang/String;)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Matching method start (()V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Applying method interceptor logger.LogbackAppender at ch/qos/logback/core/ConsoleAppender.start (()V) id:21
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method getTargetStreamForWindows ((Ljava/io/OutputStream;)Ljava/io/OutputStream;)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method isWithJansi (()Z)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method setWithJansi ((Z)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,964 Method start with signature ()V in class ch/qos/logback/core/ConsoleAppender has been successfully verified

which in this cae shows a loggin interceptor being applied.

This is briefly described here: https://docs.appdynamics.com/display/PRO43/Bytecode+Transformer+Logging

 

View solution in original post

0 Karma

Peter_Holditch
Builder

That's perfectly normal.  Tha agent logs the loading of al the classes in your application.  "no class match found" in the ByteCode log simply indicates that no rule was found that requires that the class named in the log entry be instrumented.

ie this:

[AD Thread-BCI Transform Processor0] 11 Jul 2017 10:16:44,785 Matching class name org/springframework/boot/SpringApplication Matching class bytecode. : No class match found.

Indicates that no rule matched the org.springframework.boot.SpringApplication class

You can tell what HAS been instrumented from entries like:

[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching class name ch/qos/logback/core/ConsoleAppender Matching class bytecode. : Class match found.
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method <init> (()V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method setTarget ((Ljava/lang/String;)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,959 Matching method getTarget (()Ljava/lang/String;)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Matching method targetWarn ((Ljava/lang/String;)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Matching method start (()V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,960 Applying method interceptor logger.LogbackAppender at ch/qos/logback/core/ConsoleAppender.start (()V) id:21
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method getTargetStreamForWindows ((Ljava/io/OutputStream;)Ljava/io/OutputStream;)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method isWithJansi (()Z)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,961 Matching method setWithJansi ((Z)V)
[AD Thread-BCI Transform Processor3] 11 Jul 2017 10:16:44,964 Method start with signature ()V in class ch/qos/logback/core/ConsoleAppender has been successfully verified

which in this cae shows a loggin interceptor being applied.

This is briefly described here: https://docs.appdynamics.com/display/PRO43/Bytecode+Transformer+Logging

 

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...