-
Notifications
You must be signed in to change notification settings - Fork 35
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
NETOBSERV-1617: reuse flow filter capability with pcap feature #359
NETOBSERV-1617: reuse flow filter capability with pcap feature #359
Conversation
@msherif1234: This pull request references NETOBSERV-1617 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
98d5940
to
ff1cad8
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #359 +/- ##
=======================================
Coverage ? 33.13%
=======================================
Files ? 48
Lines ? 3543
Branches ? 0
=======================================
Hits ? 1174
Misses ? 2267
Partials ? 102
Flags with carried forward coverage won't be shown. Click here to find out more.
|
if config.PCAFilters == "" { | ||
logrus.Info("[PCA] NetObserv eBPF Agent instantiated without filters to identify packets. All packets will be captured. This might cause reduced performance.") | ||
} |
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.
Do we still need a warning here in case filters are too wide ?
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.
That filter doesn’t exist anymore our option is the doc this as warning, plus if someone wanted to redirect all traffic to pcap probably they aren't looking for performance at this point
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.
yeah we need to be explicit in the doc about perf impact and implement a safe guard in case the CLI collector is getting too much data.
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=f525832 make set-agent-image |
/ok-to-test |
New image: It will expire after two weeks. To deploy this build, run from the operator repo, assuming the operator is running: USER=netobserv VERSION=82edc9f make set-agent-image |
rename all flow filters to just filter to allow reuse the same configs modify pca to use filter config update userspace, examples and doc Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com>
8ea984a
to
b658a64
Compare
Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com>
b658a64
to
e318d16
Compare
New changes are detected. LGTM label has been removed. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msherif1234 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
NOO and CLI repos need to be updated with the renamed configs
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.