-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Jmw/fentrytracer1 #51142
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
base: main
Are you sure you want to change the base?
Jmw/fentrytracer1 #51142
Changes from all commits
e6e1c09
debfdda
2ef805b
dbf4a8a
eb7a831
73ae536
2f2b19a
65f2aa2
ed6ec6a
83ebafa
7f8d2fa
7764e47
8bf7da4
e91d004
01d9ac7
7a0af9d
5afca45
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -203,7 +203,7 @@ type Config struct { | |
| // EnableEbpfless enables the use of network tracing without eBPF using packet capture. | ||
| EnableEbpfless bool | ||
|
|
||
| // EnableFentry enables the experimental fentry tracer (disabled by default) | ||
| // EnableFentry enables the fentry tracer (disabled by default, enable via config or DD_SYSTEM_PROBE_NETWORK_ENABLE_FENTRY) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The field comment says fentry is "disabled by default," but this commit sets Useful? React with 👍 / 👎. |
||
| EnableFentry bool | ||
|
|
||
| // EnableCORETracer enables the CO-RE version of the tracer | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This flips
network_config.enable_fentryto defaulttrueat runtime, but the schema still declares it asfalse(pkg/config/schema/system-probe_schema.yaml), so schema-driven outputs and tooling can disagree with actual agent behavior. That mismatch makes troubleshooting and rollout control error-prone (for example, generated/default config views show fentry off while the process enables it). Please update the schema/default metadata in the same change so all config paths agree.Useful? React with 👍 / 👎.