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
OSDOCS-7593: Netobserv RTT #67540
OSDOCS-7593: Netobserv RTT #67540
Conversation
@skrthomas: This pull request references OSDOCS-7593 which is a valid jira issue. 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 kubernetes/test-infra repository. |
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/37287 |
11e0ff9
to
b2853ee
Compare
@skrthomas: This pull request references OSDOCS-7593 which is a valid jira issue. 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 kubernetes/test-infra repository. |
b2853ee
to
9acb0b5
Compare
9acb0b5
to
38b9cf6
Compare
@skrthomas: This pull request references OSDOCS-7593 which is a valid jira issue. 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 kubernetes/test-infra repository. |
c6845ea
to
3cbcbe3
Compare
@Amoghrd @jpinsonneau This is the first draft for RTT docs. Can you PTAL and let me know your feedback? |
@skrthomas: This pull request references OSDOCS-7593 which is a valid jira issue. 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 kubernetes/test-infra repository. |
@skrthomas: This pull request references OSDOCS-7593 which is a valid jira issue. 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 kubernetes/test-infra repository. |
e063c4c
to
18c865e
Compare
Similar to what I said in the DNS PR, for RTT, it is strongly recommended to use sampling =1 for accurate metrics |
.. In the *Overview*, select new choices in *Manage panels* to choose which graphical visualizations of RTT to display. | ||
.. In the *Traffic flows* table, the *Flow RTT* column can be seen, and you can manage display in *Manage columns*. | ||
.. In the *Traffic Flows* view, you can also expand the side panel to view more information about RTT. | ||
.. Click *Common* filters -> *Protocol*. Filter the network flow data based on *Protocol TCP* to show flows with nonzero values. |
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.
We actually have some zeros in that case, even with sampling 1
https://issues.redhat.com/browse/NETOBSERV-1390
@msherif1234 is it worth putting a fancy technical limitation here ?
Or maybe just filter "Flow RTT > 0"
as mentioned below is good enough ?
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 think this bug has been closed now, and the behavior is working as expected so I don't think there's anything additional to document here. Can you confirm @msherif1234 @jpinsonneau ?
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.
probably adding Direction
= Ingress
since this measurement was done for incoming TCP traffic
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.
Got it, thanks. I re-wrote this section as "Example filtering" to try within the procedure.
/remove-label peer-review-in-progress |
32f0a3e
to
e8875dd
Compare
/remove qe-approved |
e8875dd
to
4126627
Compare
113570a
to
4b0c5fb
Compare
b2878c8
to
0ce4c68
Compare
@Amoghrd @msherif1234 I incorporated your feedback. Can you please have another look, and approve if all looks OK? |
New changes LGTM |
/LGTM |
0ce4c68
to
35aadb1
Compare
New changes are detected. LGTM label has been removed. |
For peer review/merge review:
Merge to only the no-1.5 branch - no cherrypicks are required.
This PR is part of an experiment for simplifying merges for asynchronous content, and I will open one PR against main to incorporate all of the Network Observability 1.5 content just before its GA.
Version(s):
4.11+
For Network Observability Operator 2/19/24 1.5 release.
Issue:
https://issues.redhat.com/browse/OSDOCS-7593
Link to docs preview:
Overview: https://67540--docspreview.netlify.app/openshift-enterprise/latest/network_observability/observing-network-traffic#network-observability-RTT-overview_nw-observe-network-traffic
Working with RTT: https://67540--docspreview.netlify.app/openshift-enterprise/latest/network_observability/observing-network-traffic#network-observability-RTT_nw-observe-network-traffic
QE review:
Additional information: