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
Integration between eBPF and Apps #9178
Conversation
3e40e96
to
43f9957
Compare
Neither
What kind of errors should we expect? It depends on changes? (go to summary is not clear). |
This is the motive it is |
This pull request introduces 4 alerts when merging fdca546 into f3d7624 - view on LGTM.com new alerts:
|
This pull request introduces 4 alerts when merging 2d04d4a into f3d7624 - view on LGTM.com new alerts:
|
This pull request introduces 4 alerts when merging dc04f7f into 1aa2cd7 - view on LGTM.com new alerts:
|
int collect_data_for_all_processes(ebpf_process_stat_t **out, | ||
pid_t *index, | ||
int tbl_pid_stats_fd) | ||
#endif | ||
{ |
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.
Why are you doing it this way? Why don't you assign function addresses in process_functions
depending on STATIC
macro?
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.
The kickstart_static64
will need a different structure to compile, the STATIC
is already used on netdata/kernel-collector
when we need to drop completely the shared libraries, I am keeping this here for while to keep the same pattern used on the other repository.
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.
I'm not against using STATIC
. I just prefer to do it in one place rather than several ones.
This pull request introduces 1 alert when merging eb9853c into b63d58f - view on LGTM.com new alerts:
|
@vlvkobal I observed that we are having a small problem with the conditional variables. I inserted debug messages inside the function |
I finally brought them, thank you to call my attention for this. |
Because, this was the first collector I wrote for Netdata. ;)
A big mistake, I fixed it yesterday.
Apps plugin also does not have at the end of the line both values, I am stopping on update every due the same reason. netdata/collectors/apps.plugin/apps_plugin.c Line 3202 in ba350b7
|
I could not reproduct this problem when I tested on kernel 5.6.17.
We really had a problem for
The same thing happens on these distribution, they were affected for the same bug. @vlvkobal , please, can you test them again? I am also testing on other kernels here. |
CentOS 8 and Ubuntu have special kernels. For CentOS 8 we have a specific script to compile for it, I will take a look on it now. |
@vlvkobal i am not sure we should test for Fed 30 as it is EOL soon |
Manage this branch in SquashTest this branch here: https://thiagoftsmebpf-apps-ox6u7.squash.io |
Summary
Fixes #8912
Fixes #8914
This PR brings the integration between the collectors eBPF and Apps.
Component Name
Collector
Test Plan
1 - Install Netdata using
./netdata-installer.sh --dont-start-it
.2 - Download the file files4.zip and extract it inside
/usr/libexec/netdata/plugins.d
.3 - Run netdata and verify the charts on
apps.plugin
.4 - Stop netdata after few seconds.
5 - Start netdata again.
Do the steps 4 and 5 at least 3 times. We should have consistency on all charts (general and apps) in all tests.
It is expected to see 14 charts inside apps submenu.
Additional Information