search cancel

Unknown SQL - SkipClass not working

book

Article ID: 215622

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

 

Using the 21.4 agent to monitor Atlassian Jira running in Tomcat using Oracle 19c driver, there are some Unknown SQL metrics reported in transaction traces based on the class

com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement

Attempts to skip the whole class, or skip from SQLAgentStatements tracer group in sqlagent.pbd but the element still appears in the transaction trace.

Unknown SQL metrics are not reported because valid SQL statements, obtained from other classes, are reported closer to the backend exit point.

Environment

Release : 20.2

Component : APM Agents

Resolution

 
 

Necessary to combine multiple skip instructions to make sure the class and inherited classes are skipped:

SkipClass: com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement
SkipClassForFlag: com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement SQLAgentStatements
SkipIfInheritedForFlag: com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement SQLAgentStatements

Attachments