Spring uses "SELECT 1" to health check the connection to database which
gets traced by default. Rather forcing systems with a DB health check to
set "traceWithActiveSpanOnly" to false this patch allows certain queries
to be entirely ignored by the tracer.
We've just started deploying the JDBC tracer to our infrastructure, and it's really great to see the queries
from each rest call as part of the trace but our Zipkin UI is drowning in thousands of "SELECT 1" traces.
We'd rather not be forced to set "traceWithActiveSpanOnly" because we'd like to understand where and
how there is database access without an existing trace scope.
Spring uses "SELECT 1" to health check the connection to database which gets traced by default. Rather forcing systems with a DB health check to set "traceWithActiveSpanOnly" to false this patch allows certain queries to be entirely ignored by the tracer.
We've just started deploying the JDBC tracer to our infrastructure, and it's really great to see the queries from each rest call as part of the trace but our Zipkin UI is drowning in thousands of "SELECT 1" traces. We'd rather not be forced to set "traceWithActiveSpanOnly" because we'd like to understand where and how there is database access without an existing trace scope.