-
Notifications
You must be signed in to change notification settings - Fork 110
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
Fix wrong reported program type and missing traces #552
Conversation
@@ -130,7 +131,7 @@ static __always_inline u8 correlated_requests(tp_info_pid_t *tp, tp_info_pid_t * | |||
// We check for correlated requests which are in order, but from different PIDs | |||
// Same PID means that we had client port reuse, which might falsely match prior | |||
// transaction if it happened during the same epoch. | |||
if ((tp->tp.ts > existing_tp->tp.ts) && (tp->pid != existing_tp->pid)) { | |||
if ((tp->tp.ts >= existing_tp->tp.ts) && (tp->pid != existing_tp->pid)) { |
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.
These could be the same if the requests are too quick to happen one after another.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #552 +/- ##
===========================================
- Coverage 79.32% 45.04% -34.28%
===========================================
Files 69 67 -2
Lines 5828 5652 -176
===========================================
- Hits 4623 2546 -2077
- Misses 984 2955 +1971
+ Partials 221 151 -70
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
🙌🏻
When we were re-using the process tracers we weren't setting the program type on the service id. It would only be seen by duplicated executables, which we have plenty of in multi-exec. I also found that we weren't pinning certain maps which held the information on currently processed traces, so depending on which kernel program ran we might miss some trace events. I also fixed some prints which were on when debug was disabled.
Closes #532