| 1 | # The `ebpf load mode` option accepts the following values : |
| 2 | # `entry` : The eBPF collector only monitors calls for the functions, and does not show charts related to errors. |
| 3 | # `return : In the `return` mode, the eBPF collector monitors the same kernel functions as `entry`, but also creates |
| 4 | # new charts for the return of these functions, such as errors. |
| 5 | # |
| 6 | # The eBPF collector also creates charts for each running application through an integration with the `apps.plugin` |
| 7 | # or `cgroups.plugin`. |
| 8 | # If you want to disable the integration with `apps.plugin` or `cgroups.plugin` along with the above charts, change |
| 9 | # the setting `apps` and `cgroups` to 'no'. |
| 10 | # |
| 11 | # The `ebpf type format` option accepts the following values : |
| 12 | # `auto` : The eBPF collector will investigate hardware and select between the two next options. |
| 13 | # `legacy`: The eBPF collector will load the legacy code. Note: This has a bigger overload. |
| 14 | # `co-re` : The eBPF collector will use latest tracing method. Note: This is not available on all platforms. |
| 15 | # |
| 16 | # The `ebpf co-re tracing` option accepts the following values: |
| 17 | # `trampoline`: This is the default mode used by the eBPF collector, due the small overhead added to host. |
| 18 | # `probe` : This is the same as legacy code. |
| 19 | # |
| 20 | # The `maps per core` defines if hash tables will be per core or not. This option is ignored on kernels older than 4.6. |
| 21 | # |
| 22 | # The `lifetime` defines the time length a thread will run when it is enabled by a function. |
| 23 | # |
| 24 | # Uncomment lines to define specific options for thread. |
| 25 | [global] |
| 26 | # ebpf load mode = entry |
| 27 | # apps = yes |
| 28 | # cgroups = no |
| 29 | # update every = 10 |
| 30 | # pid table size = 32768 |
| 31 | ebpf type format = auto |
| 32 | ebpf co-re tracing = trampoline |
| 33 | collect pid = real parent |
| 34 | # maps per core = yes |
| 35 | lifetime = 300 |