-
Notifications
You must be signed in to change notification settings - Fork 6
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-2021 Improve UX #146
base: main
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
function setLastFlowFilter() { | ||
"$YQ_BIN" e --inplace " .spec.template.spec.containers[0].env[] |= select(.name == \"FLOW_FILTER_RULES\").value |=(fromjson | .[-1].$1 = $2 | tostring)" "$3" | ||
} | ||
|
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 u have sample output with mutli rule, I have standalone script fo ut this logic maybe we bring this in and intg with ut ci as logic start to become complex ?
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.
Sure. I will add examples and tests !
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 have added the following scenarios for now:
basic examples:
netobserv flows --drops # Capture dropped flows on all nodes
netobserv packets --port=8080 # Capture packets on port 8080
netobserv metrics --enable_all # Capture all cluster metrics with pktDrop, dns, rtt and network events features
advanced examples:
Capture drops in background and copy output locally
netobserv flows --background \ # Capture flows using background mode
--max-time=15m \ # for a maximum of 15 minutes
--protocol=TCP --port=8080 \ # either on TCP 8080
or --protocol=UDP # or UDP
netobserv follow # Display the progression of the background capture
netobserv stop # Stop the background capture by deleting eBPF agents
netobserv copy # Copy the background capture output data
netobserv cleanup # Cleanup netobserv CLI by removing the remaining collector pod
Capture packets on specific nodes and port
netobserv packets # Capture packets
--node-selector=netobserv:true \ # on nodes labelled with netobserv=true
--port=80 \ # on port 80 only
--max-bytes=100000000 # for a maximum of 100MB
Please let me know if you feel more would be useful
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.
can u pls include example with mutli rules ?
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.
You have one above in the advanced examples 😸
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #146 +/- ##
==========================================
+ Coverage 22.51% 23.45% +0.93%
==========================================
Files 11 11
Lines 1310 1326 +16
==========================================
+ Hits 295 311 +16
+ Misses 999 998 -1
- Partials 16 17 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
BTW if u added the rules in reverse order this will break filtering , rules has to place in the json array in the same order they are configured. |
The order is kept as I append the whole json from this file: https://github.com/netobserv/network-observability-cli/blob/994f4b4888d67fc72f1a90cd72d4295a50614507/res/flow-filter.json However we should document this behavior as it's can break easily ! |
/retest |
1 similar comment
/retest |
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.
Just a few nitties 👼 , and otherwise LGTM! Thanks Julien :)
/ok-to-test |
New image: It will expire after two weeks. To use this build, update your commands using: USER=netobserv VERSION=ac57fb3 make commands |
Rebased without changes |
/LGTM |
/retest |
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.
/lgtm
New image: It will expire after two weeks. To use this build, update your commands using: USER=netobserv VERSION=1d1df34 make commands |
@jotak is it worth replacing UDN column by network names here in the end ? I see the UDNs column is still there as before so that's covered in this PR. We can create a followup for NetworkNames if needed as it impacts the pipeline as you mentionned in today's scrum |
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.
@jpinsonneau thanks for addressing UX issues. It looks great.
quick question: when I enable packet translation, how do I get that view?
You can use |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jpinsonneau yes, I did use |
@memodi don't you get that output ? |
/ok-to-test |
New image: It will expire after two weeks. To use this build, update your commands using: USER=netobserv VERSION=479b4f5 make commands |
@jpinsonneau I am testing network names, but I am not able to see the network names that I am expecting, I am using "--enable_all" , am I missing something? I confirmed I am able see it on operator side. |
Description
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.