fix: Rename op db to db.query (#4444)

- According to our [span
ops](https://develop.sentry.dev/sdk/telemetry/traces/span-operations/#database)
there is no op called just `db`, but we're emitting these from django,
clickhouse, asyncpg and pymongo. Changing to `db.query` instead.
- There was also a breadcrumb with type `db` that's also [officially not
a supported
type](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/#breadcrumb-types),
changed it to `query`.

This is intentionally just on `potel-base` since it's technically a
breaking change.

Author: sentrivana

MIGRATION_GUIDE.md

@@ -19,6 +19,7 @@ Looking to upgrade from Sentry SDK 2.x to 3.x? Here's a comprehensive list of wh
 - The `sentry_sdk.Scope()` constructor no longer accepts a `client` parameter.
 - `Span.finish()` does not accept a `hub` parameter anymore.
 - `Span.finish()` no longer returns the `event_id` if the event is sent to sentry.
+- Some integrations were creating spans with `op` `db`. This was changed to `db.query`.
 - The `Profile()` constructor does not accept a `hub` parameter anymore.
 - A `Profile` object does not have a `.hub` property anymore.
 - `MAX_PROFILE_DURATION_NS`, `PROFILE_MINIMUM_SAMPLES`, `Profile`, `Scheduler`, `ThreadScheduler`, `GeventScheduler`, `has_profiling_enabled`, `setup_profiler`, `teardown_profiler` are no longer accessible from `sentry_sdk.profiler`. They're still accessible from `sentry_sdk.profiler.transaction_profiler`.
@@ -31,6 +32,7 @@ Looking to upgrade from Sentry SDK 2.x to 3.x? Here's a comprehensive list of wh
 - We updated how we handle `ExceptionGroup`s. You will now get more data if ExceptionGroups are appearing in chained exceptions. It could happen that after updating the SDK the grouping of issues change because of this. So eventually you will see the same exception in two Sentry issues (one from before the update, one from after the update)
 - The integration for Python `logging` module does not send Sentry issues by default anymore when calling `logging.error()`, `logging.critical()` or `logging.exception()`. If you want to preserve the old behavior use `sentry_sdk.init(integrations=[LoggingIntegration(event_level="ERROR")])`.
 - The `SentrySpanProcessor` and `SentryPropagator` are exported from `sentry_sdk.opentelemetry` instead of `sentry_sdk.integrations.opentelemetry`.
+- PyMongo breadcrumb type was changed from `db` to `query`.
 - The integration-specific content of the `sampling_context` argument of `traces_sampler` and `profiles_sampler` now looks different.
 
   - The Celery integration doesn't add the `celery_job` dictionary anymore. Instead, the individual keys are now available as:

sentry_sdk/consts.py

@@ -496,7 +496,7 @@ class OP:
     CACHE_PUT = "cache.put"
     COHERE_CHAT_COMPLETIONS_CREATE = "ai.chat_completions.create.cohere"
     COHERE_EMBEDDINGS_CREATE = "ai.embeddings.create.cohere"
-    DB = "db"
+    DB_QUERY = "db.query"
     DB_REDIS = "db.redis"
     EVENT_DJANGO = "event.django"
     FUNCTION = "function"

sentry_sdk/integrations/asyncpg.py

@@ -163,7 +163,7 @@ async def _inner(*args: Any, **kwargs: Any) -> T:
             return await f(*args, **kwargs)
 
         with sentry_sdk.start_span(
-            op=OP.DB,
+            op=OP.DB_QUERY,
             name="connect",
             origin=AsyncPGIntegration.origin,
             only_if_parent=True,

sentry_sdk/integrations/clickhouse_driver.py

@@ -85,7 +85,7 @@ def _inner(*args: P.args, **kwargs: P.kwargs) -> T:
         params = args[3] if len(args) > 3 else kwargs.get("params")
 
         span = sentry_sdk.start_span(
-            op=OP.DB,
+            op=OP.DB_QUERY,
             name=query,
             origin=ClickhouseDriverIntegration.origin,
             only_if_parent=True,

sentry_sdk/integrations/django/__init__.py

@@ -660,7 +660,7 @@ def connect(self):
             sentry_sdk.add_breadcrumb(message="connect", category="query")
 
         with sentry_sdk.start_span(
-            op=OP.DB,
+            op=OP.DB_QUERY,
             name="connect",
             origin=DjangoIntegration.origin_db,
             only_if_parent=True,

sentry_sdk/integrations/pymongo.py

@@ -150,15 +150,15 @@ def started(self, event):
 
             query = _serialize_span_attribute(command)
             span = sentry_sdk.start_span(
-                op=OP.DB,
+                op=OP.DB_QUERY,
                 name=query,
                 origin=PyMongoIntegration.origin,
                 only_if_parent=True,
             )
 
             with capture_internal_exceptions():
                 sentry_sdk.add_breadcrumb(
-                    message=query, category="query", type=OP.DB, data=data
+                    message=query, category="query", type="query", data=data
                 )
 
             for key, value in data.items():

sentry_sdk/opentelemetry/utils.py

@@ -219,7 +219,7 @@ def span_data_for_db_query(span):
     # type: (ReadableSpan) -> OtelExtractedSpanData
     span_attributes = span.attributes or {}
 
-    op = cast("str", span_attributes.get(SentrySpanAttribute.OP, OP.DB))
+    op = cast("str", span_attributes.get(SentrySpanAttribute.OP, OP.DB_QUERY))
 
     statement = span_attributes.get(SpanAttributes.DB_STATEMENT, None)
     statement = cast("Optional[str]", statement)

sentry_sdk/tracing_utils.py

@@ -151,7 +151,7 @@ def record_sql_queries(
         sentry_sdk.add_breadcrumb(message=query, category="query", data=data)
 
     with sentry_sdk.start_span(
-        op=OP.DB,
+        op=OP.DB_QUERY,
         name=query,
         origin=span_origin,
         only_if_parent=True,