Discussion Feed

Josh,   The fact that you see the Connect instrumentation applied is encouraging!  Do you also see instrumentation applied for callable statements, prepared statements etc.?   If not, you may be using a version of the Postgres jdbc driver that is not covered by the out of the box agent configuration.  In this case, you can configure the implementation classes to to picked up using the relevant jdbc-* agent properties.   If it happens that you're using v9.4+ of the Postgres driver, the settings should be: jdbc-statements: value= "org.postgresql.jdbc.PgStatement" jdbc-connections: value= "org.postgresql.jdbc.PgConnection" jdbc-prepared-statements: value= "org.postgresql.jdbc.PgPreparedStatement" jdbc-callable-statements: value= "org.postgresql.jdbc.PgCallableStatement"   If this isn't the issue, then another possibility is that the jdbc activity is happening on a thread that has not been tracked by the agent.  You can tell if this is the case using the uninstrumented code detection feature, and configure the missing thread handoffs in the agent's fork-config configuration, or the thread-correlation-classes agent property.   Warm regards, Peter.   ... View more