Skip to content

fix(python): Correct functions_to_trace option type #19819

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sentrivana merged 1 commit into from
Oct 6, 2026
Merged

fix(python): Correct functions_to_trace option type #19819

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/platforms/python/configuration/options.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -534,10 +534,10 @@ The organization ID is used for features like <PlatformLink to="/configuration/o

</SdkOption>

<SdkOption name="functions_to_trace" type='list[str]' defaultValue='[]'>
<SdkOption name="functions_to_trace" type='list[dict[str, str]]' defaultValue='[]'>

An optional list of functions that should be set up for tracing. For each function in the list, a span will be created when the function is executed.
Functions in the list are represented as strings containing the fully qualified name of the function.
Each entry is a dictionary with a `qualified_name` key that holds the fully qualified name of the function, for example `{"qualified_name": "myapp.utils.my_function"}`.

This is a convenient option, making it possible to have one central place for configuring what functions to trace, instead of having custom instrumentation scattered all over your code base.

Expand Down
Loading