disable network-socket-tracing function (ebpf) #16923
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
area/collectors
|
@ilyam8 unless we modified something, this already worked before. Set to NULL is enough to disable. |
ilyam8
force-pushed
the
disable-ebpf-network-socket-tracing
branch
from
68e1f3e
to
d61fbdb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Because it has issues (e.g. a lot of process names are "unknown" for some reason) and in its current state is generally inferior to the "network connections" function. And it is confusing for users to have both (see this Slack discussion).
@thiagoftsm I couldn't find a way to disable it via a configuration option. It seems it is always enabled no matter what 馃し.
Test Plan
No "network-socket-tracing" in the Top tab.
Additional Information
For users: How does this change affect me?