-
Notifications
You must be signed in to change notification settings - Fork 15
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-1227 NETOBSERV-1388: Max / P90 / P99 graphs #412
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #412 +/- ##
==========================================
- Coverage 58.75% 57.89% -0.86%
==========================================
Files 140 168 +28
Lines 5976 8407 +2431
Branches 999 1060 +61
==========================================
+ Hits 3511 4867 +1356
- Misses 2303 3228 +925
- Partials 162 312 +150
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@jotak & @OlivierCazade could you please take a look at this draft so we can validate the approach ? Thanks ! |
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=6fc9562 make set-plugin-image |
@jpinsonneau: This pull request references NETOBSERV-1227 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.15.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 kubernetes/test-infra repository. |
Hmm in fact I was not thinking something that generic, as an approach. I think we need to distinguish two kinds of metrics:
So I think we should restrict these new charts to only latencies (RTT and DNS) |
Sure, makes sense to me. I removed the new charts from rates ones and took the opportunity to save all the metrics in a single state so it will be easier to update in the future. |
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=154f5c8 make set-plugin-image |
@jpinsonneau: This pull request references NETOBSERV-1227 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.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
/label qe-approved |
@jpinsonneau: This pull request references NETOBSERV-1388 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 bug to target the "4.15.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 kubernetes/test-infra repository. |
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=9c09670 make set-plugin-image |
In topology side panel, I guess we should filter-out 0ms latencies prior to any calculation: (I guess the 0ms come from the normalization of the metrics, which makes more sense with rate-like metrics than latencies/histograms. Not sure what would be the side-effects if we remove this NaN-to-0 normalization for latencies - it's either this, or filtering-out 0s I guess) Also, a UX remark on the topology side-panel: as we are adding more metrics I find it not very convenient that the "metric type" setting is shared between topology view (graph edges) and that side panel. I didn't realize immediately that to see other metrics I had to go back in the advanced /display options. We could even show a bit more than just a single selected metric type. I can create a story to suggest an enhancement here, for another release. |
done with the review, I've found just 2 issues, after that it's lgtm, nice work! |
Thanks for your feedback @jotak ! It seems indeed that
That's why the graph were showing zeros on
Also skipped the normalization for dns & rtt queries and forced
Could you please create a followup for this ? I'm open to any suggestions here |
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=d97e766 make set-plugin-image |
@jpinsonneau I still see the hole next to donut graphs, is that going to be fixed in another PR or in this itself? Could also confirm the DNS metrics are now seen for all edge labels |
This PR is not solving that yet. I was waiting for a decision in that thread: I'm fine merging as is and doing a followup if we are not fixed yet 😉 |
/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=81e04ef make set-plugin-image |
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
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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
Add functions for time based metrics (DNS Latency / RTT):
Related changes:
These changes will also fix NETOBSERV-1388
Dependencies
Based on #405
Panel ids will need update in #424
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.