Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Document / Fix Spring Monitoring

Description

Currently, I’m trying to get Micro-company ( ) running with Kieker. This is a microservice example application that has been used in some case studies.

Unfortunately, monitoring does not work and Kiekers slf4j-versions block logging, so I also do not get any error messages. After building my fork ( ) on the master branch (mvn clean install -DskipTests), the application can be started regularly in monolithic/target/docker using java -cp monolithic-0.0.1-SNAPSHOT.jar org.springframework.boot.loader.JarLauncher.

Adding the javaagent with default configurations ends with no logs:

java -javaagent:kieker-1.15.4-aspectj.jar -cp monolithic-0.0.1-SNAPSHOT.jar org.springframework.boot.loader.JarLauncher

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

and with a lot of logging data, that are only spring of logback data:

reichelt@reichelt-desktop:~/nvme/workspaces/kiekerworkspace/micro-company/monolithic/target/docker$ cat /tmp/kieker-20240315-144756-21219659539625-UTC--KIEKER-SINGLETON/kieker*dat | wc -l
7928688

These records are mostly spring-internal things, e.g., org.springframework.boot.loader.jar.JarFileEntries.swap

After these ~7 million records, nothing happens (no more kieker entries, no response from the application via http, no logs). The application is not started in this configuration, so for some reason, adding the javaagent to a spring application in this context stops the spring application from being executed.

To overcome this, I tried to only instrument the idugalic package thing, with the following kieker.aop.xml:

<!DOCTYPE aspectj PUBLIC "-//AspectJ//DTD//EN" "http://www.aspectj.org/dtd/aspectj_1_5_0.dtd">
<aspectj>
<weaver options="-verbose">
<include within="com.idugalic..*" />
</weaver>
<aspects>
<aspect
name="kieker.monitoring.probe.aspectj.operationExecution.OperationExecutionAspectFull" />
</aspects>
</aspectj>

Using this, the application is functional from the outside, but still does not get logs (not even /tmp/kieker-XYZ is created - logfile is attached).

For debugging the AspectJ behavior, I think its necessary to get the logging right. Unfortunately, spring (or the 1.5.3 version, which is used here) does not work together with Kieker, even when just adding Kieker to the classpath (java -cp monolithic-0.0.1-SNAPSHOT.jar:kieker-1.15.4-aspectj.jar org.springframework.boot.loader.JarLauncher), the logging stops to work. Also adding the slf4j and logback libraries in the version that are normally used (java -cp monolithic-0.0.1-SNAPSHOT.jar:BOOT-INF/lib/slf4j-api-1.7.25.jar:BOOT-INF/lib/logback-core-1.1.11.jar:BOOT-INF/lib/logback-classic-1.1.11.jar org.springframework.boot.loader.JarLauncher) does not fix this problem.

According to new relic, adding a javaagent directly to spring should just work ( ), the documentation about spring instrumentation with Kieker is unfortunately empty ( ).

Is there any way to get Kieker runnable with an older slf4j / spring version, and if yes, how?

Attachments

1

Activity

David Georg Reichelt April 9, 2024 at 3:24 PM

I made some progress here:

  • spring-boot-starter-aop and kieker spring needs to be added:

  • To activate spring interception, a spring-config.xml is necessary:

  • When starting the application, the configuration needs to be specified (as its done with kiekers own spring demo: )

  • This requires definition of an own spring jar:

Currently, this initializes the OperationExecutionMethodInvocationInterceptor , but does not call the invoke method.

Additionally, if kieker includes slf4j-api 1.7.30, Spring always fails. Updating to 2.0.12 fixes this (and is the version currently used by spring), but I’m not sure whether this will have side effects on other projects. As far as I understand , it shouldn’t be a problem.

David Georg Reichelt April 8, 2024 at 4:16 PM

The current spring demo works, but it doesn’t use spring boot, so this is not really compatible. Nevertheless, I’ve updated the versions here, and everything seems to run fine.

David Georg Reichelt March 15, 2024 at 4:30 PM

Having a further look at this, this is not only related to micro-company, but there seems to be some problem with Kiekers packaging.

In the following demo project: if we start this with kiekers javaagent, it seems like logback somehow got into the agent:

reichelt@reichelt-desktop:~/nvme/workspaces/kiekerworkspace/spring-demo$ java -Dorg.aspectj.weaver.loadtime.configuration=kieker.aop.xml -javaagent:kieker-1.15.4-aspectj.jar -jar target/demo-0.0.1-SNAPSHOT.jar
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See for further details.
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:91)
at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:53)
at org.springframework.boot.loader.launch.JarLauncher.main(JarLauncher.java:58)
Caused by: java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.slf4j.helpers.NOPLogg
erFactory loaded from file:/home/reichelt/nvme/workspaces/kiekerworkspace/spring-demo/kieker-1.15.4-aspectj.jar). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-
INF/weblogic.xml: org.slf4j.helpers.NOPLoggerFactory
at org.springframework.util.Assert.instanceCheckFailed(Assert.java:592)
at org.springframework.util.Assert.isInstanceOf(Assert.java:511)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:396)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:124)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:238)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:220)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:185)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:178)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:156)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
at org.springframework.boot.context.event.EventPublishingRunListener.multicastInitialEvent(EventPublishingRunListener.java:136)
at org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:75)
at org.springframework.boot.SpringApplicationRunListeners.lambda$starting$0(SpringApplicationRunListeners.java:54)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:118)
at org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:54)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:326)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1343)
at net.kiekertest.demo.DemoApplication.main(DemoApplication.java:10)
... 7 more

Lets discuss this at the next meeting.

David Georg Reichelt March 15, 2024 at 3:40 PM

Update: I’ve tried it with Kieker 1.13, when using this, the logs don’t disappear:

However, no kieker traces are created. Since it says

INFORMATION: Using Kieker's AspectJLoader. This is not recommended for multi-classloader environments such as JavaEE and OSGI. Use the additional VM parameter '-Dkieker.monitoring.skipDefaultAOPConfiguration=true'. to disable Kieker's AspectJLoader

I’ve tried it using this configuration, but this doesn’t change anything, besides the message disappearing - still, no kieker trace is created, not even a folder (which indicates that instrumentation doesn’t seem to work at all).

Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Affects versions

Priority

Created March 15, 2024 at 3:04 PM
Updated April 9, 2024 at 3:24 PM