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

Add a built-in trace interceptor for keeping traces depending of their latency #8040

Merged
merged 8 commits into from
Dec 5, 2024
Merged
Changes from 1 commit
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
Prev Previous commit
Next Next commit
improve comments
  • Loading branch information
Cecile Terpin committed Nov 29, 2024
commit 955e3822172b01cbffff35eb6fcd960720bccbd8
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,11 @@
// This value should be in milliseconds and this interceptor will retain any local trace who has a
// root
// span duration greater than this value.
// The activation of this interceptor is ignored if partial flush is enabled.
// The activation of this interceptor is ignored if partial flush is enabled in order to avoid
// incomplete local trace (incomplete chunk of trace).
// Note that since we're changing the sampling priority at the end of local trace, there is no
// guarantee to get complete traces,
// since the original sampling priority for this trace may have been already propagated.
// since the original sampling priority for this trace may have already been propagated.

public class LatencyTraceInterceptor extends AbstractTraceInterceptor {
private static final Logger log = LoggerFactory.getLogger(LatencyTraceInterceptor.class);
Expand Down
Loading