skywalking could not get the trace info between sonarqube(7.6) and mysql(5.7) which works well between sonarqube(8.9) and postsql(13.8) #10891
-
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
|
By the way, the skywalking-oap verion I use is 9.2. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think we have sonarqube plugin at all, do we? |
Beta Was this translation helpful? Give feedback.
-
|
Sonarqube support both JDBC with mysql or postsql, the only different is before sonar7.8 mysql supported , after sonar7.8 mysql not supported. |
Beta Was this translation helpful? Give feedback.
-
|
Do we need any special plugin for sonarque in skywalking? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I see. I actually want to know if I miss any necessary plugins or deploy parameters when use skywalking trace mysql, since I just start to learn how to use it. Maybe I could change to try another application(not sonar) with mysql. Any suggestion for the demo configuration for tracing mysql? |
Beta Was this translation helpful? Give feedback.

My issue resolved by mount sonar.properties file out of container to set Java env values shown below. It's done. Seems the Java env not take effect when just set in .yaml file.
sonar.web.javaOpts=-Xmx1024m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -javaagent:/skywalking/agent/skywalking-agent.jar
sonar.web.javaAdditionalOpts=-javaagent:/skywalking/agent/skywalking-agent.jar