[Feature] How to Disable Mysql/JDBC/Connection/close from Showing in SkyWalking Trace Segments

[stoneLee81]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

There are many Mysql/JDBC/Connection/close entries in the SkyWalking reports. How can I prevent them from showing up?

Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

This is caused by your connection pool. It created or closed when idel or busy.

You can't disable it, unless you change plugin codes to remove codes which make close disappeared from other tracing(normal trace).

[stoneLee81]

This is caused by your connection pool. It created or closed when idel or busy.

You can't disable it, unless you change plugin codes to remove codes which make close disappeared from other tracing(normal trace).

However, when I view the trace segments sorted by time to analyze the most recent requests, the top entries are all these kinds of useless traces like Mysql/JDBC/Connection/close. This seriously affects report readability. Do you have any other suggestions to solve this problem?

[wu-sheng]

You should not filter traces only by time. Usually, we use trace ID, tags, time range to filter out traces, the with this sort.