Skip to content
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.

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

docs: update trace filter docs #12147

Merged
merged 1 commit into from
Jan 29, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
8 changes: 2 additions & 6 deletions docs/advanced_usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -342,11 +342,7 @@ all traces of incoming requests to a specific url::
return None
return trace

tracer.configure(settings={
'FILTERS': [
FilterbyName(),
],
})
tracer.configure(trace_processors=[FilterbyName()])

The filters in the filters list will be applied sequentially to each trace
and the resulting trace will either be sent to the Agent or discarded.
Expand All @@ -367,7 +363,7 @@ the pipeline or ``None`` if the trace should be discarded::
...

# And then configure it with
tracer.configure(settings={'FILTERS': [FilterExample()]})
tracer.configure(trace_processors=[FilterExample()])

(see filters.py for other example implementations)

Expand Down
2 changes: 1 addition & 1 deletion docs/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ While this is default behavior for integrations, users can add a trace filter to
return trace


tracer.configure(settings={'FILTERS': [ErrorFilter()]})
tracer.configure(trace_processors=[ErrorFilter()])



Expand Down
Loading