From 60ef0f220ad4e74819f5344842f592ff6553b910 Mon Sep 17 00:00:00 2001 From: William Mak Date: Wed, 9 Oct 2024 16:59:38 -0400 Subject: [PATCH] fix(span): ADd replacement column for transaction.id (#78862) - Replacing `transaction.id` and `span.id` for `transaction.span_id`. Leaving them in cause the frontend might still be using them --- src/sentry/utils/snuba.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/sentry/utils/snuba.py b/src/sentry/utils/snuba.py index dd9ccdcfe25f9e..6efc45cbbeacf7 100644 --- a/src/sentry/utils/snuba.py +++ b/src/sentry/utils/snuba.py @@ -136,6 +136,7 @@ def log_snuba_info(content): "transaction": "segment_name", "transaction.id": "transaction_id", "segment.id": "segment_id", + "transaction.span_id": "segment_id", "transaction.op": "transaction_op", "user": "user", "user.id": "sentry_tags[user.id]", @@ -198,7 +199,11 @@ def log_snuba_info(content): "timestamp": "timestamp", "trace": "trace_id", "transaction": "segment_name", + # `transaction.id` and `segment.id` is going to be replaced by `transaction.span_id` please do not use + # transaction.id is "wrong", its pointing to segment_id to return something for the transistion, but represents the + # txn event id(32 char uuid). EAP will no longer be storing this. "transaction.id": "segment_id", + "transaction.span_id": "segment_id", "transaction.method": "attr_str[transaction.method]", "is_transaction": "is_segment", "segment.id": "segment_id",