getsentry / getsentry/sentry-java
Add SQL span data
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.4k
- Forks
- 478
- Merge medio
- 2 d 23 h
- PR fusionados (30 d)
- 67
Descripción
### Problem Statement
First-party JDBC and Android SQLite spans currently keep the SQL statement only in the span description and attach limited database metadata (`db.system` and `db.name`). They do not attach `db.query.text` or generate `db.query.summary`.
### Solution Brainstorm
Attach database query semantic data to first-party JDBC and Android SQLite spans:
- `db.query.text`: the parameterized or SDK-sanitized statement. We should run this through a sanitizer.
- `db.query.summary`: a low-cardinality operation/target summary such as `UPDATE users`.
- Consider attaching analyzer-derived operation, collection/table, and stored-procedure attributes where they match Sentry conventions.
Check sentry conventions for more (query derived) attributes we can attach.
There's currently no data collection option to gate sanitized/parameterized `db.query.text` or `db.query.summary` so we can just attach them. Best double check https://develop.sentry.dev/sdk/foundations/client/data-collection/ when implementing.
Closely related to https://github.com/getsentry/sentry-java/issues/6019
Guía de contribución
Línea de trabajo
Start by locating the first-party JDBC and Android SQLite span instrumentation, then review Sentry database conventions and the linked issue 6019. Check the data-collection guidance before implementation. Done means the relevant spans attach sanitized or parameterized db.query.text and low-cardinality db.query.summary, with matching derived attributes where applicable.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, java, kotlin, sqlite
- Área
- databases, observability
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100