Skip to content

Conversation

@trask
Copy link
Member

@trask trask commented Dec 5, 2025

No description provided.

@trask trask force-pushed the db-query-summary-sql branch 4 times, most recently from add6c0a to b7451ce Compare December 6, 2025 00:14
@trask trask force-pushed the db-query-summary-sql branch from f299e7c to c5970ae Compare December 6, 2025 15:44
Comment on lines +155 to +157
equalTo(
DbAttributes.DB_QUERY_SUMMARY,
emitStableDatabaseSemconv() ? "CALL" : null)),
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be CALL NEXT VALUE?

@trask trask force-pushed the db-query-summary-sql branch from b736229 to 2b193cd Compare December 7, 2025 19:19
@trask trask force-pushed the db-query-summary-sql branch from a10beca to 2aa9083 Compare December 8, 2025 21:04
trask added 4 commits December 8, 2025 14:59
When SQL query text cannot be parsed (e.g., invalid SQL or non-SQL text),
the span name was incorrectly falling back to server.address instead of
the default 'DB Query' name.

According to semconv, server.address should only be used as part of the
target when combined with an operation (e.g., 'SELECT localhost'). When
there is no operation, the fallback should be db.system.name or the
default span name.

This change ensures that server.address is only used when we have a
valid operation to combine it with, preventing span names like
'localhost' when the SQL cannot be parsed.

Fixes failing tests in:
- :instrumentation:jdbc:javaagent:testStableSemconv
- :instrumentation:jdbc:library:testStableSemconv
- :instrumentation:cassandra:cassandra-3.0:javaagent:testStableSemconv
Per the stable database semantic conventions, when neither operation
nor target are available, the span name should be db.system.name.

Updated the test to expect 'other_sql' (the db.system.name value) for
stable semconv, while keeping 'DB Query' for old semconv to maintain
backward compatibility.
@trask trask force-pushed the db-query-summary-sql branch from e761302 to 69592b0 Compare December 9, 2025 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant