Skip to content

fix: Remove manual config section from python span lifecycle page #13319

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
merged 1 commit into from
Apr 11, 2025
Merged

fix: Remove manual config section from python span lifecycle page #13319

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
5 changes: 0 additions & 5 deletions docs/platforms/python/tracing/span-lifecycle/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,6 @@ To add custom performance data to your application, you need to add custom instr

<PlatformContent includePath="enriching-events/import" />

There are two main approaches to creating spans in Python:

- [Using the context manager](#using-the-context-manager): Creates a span with an automatic lifecycle (recommended).
- [Manual span creation](#creating-spans-manually): Gives you more control over the span's lifecycle.

## Span Lifecycle

In Python, spans are typically created using a context manager, which automatically manages the span's lifecycle. When you create a span using a context manager, the span automatically starts when entering the context and ends when exiting it. This is the recommended approach for most scenarios.
Expand Down