getsentry / getsentry/sentry

Support non-deprecated `code.function.name` for code source

Open
#113,884 2 comments 0 reactions 0 assignees View on GitHub
python Traces
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

We are considering setting the non-deprecated `code.function.name` in the Python SDK.

Today the function displayed in the code source panel is only drawn from `code.function`.

Note that `code.function.name` is not equivalent to `code.function`, as `code.function.name` is the fully-qualified name [as per OTel](https://opentelemetry.io/docs/specs/semconv/registry/attributes/code/#code-function-name), while `code.function` is only the function identifier. That is, `code.function.name` includes both the values of the deprecated `code.namespace` and the deprecated `code.function`.

Setting `code.function`:

Image

Setting `code.function.name`:

Image

### Solution Brainstorm

_No response_

### Product Area

Explore

Contributor guide

Open the contributing guide

Research direction

The issue does not identify a file, test, or entry point. Start by locating the code-source panel's handling of code.function in the Sentry Python SDK and compare it with the linked OpenTelemetry definition. Done means the panel supports the non-deprecated, fully qualified code.function.name value and its display behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.