Skip to content
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

Merged
merged 3 commits into from
Dec 11, 2023

Conversation

jpinsonneau
Copy link
Contributor

@jpinsonneau jpinsonneau commented Oct 12, 2023

Description

Add functions for time based metrics (DNS Latency / RTT):

  • min
  • max
  • P90
  • P99

Related changes:

  • refactor of overview page / graphs
  • new metrics on topology labels
  • query summary
  • improved testing using a list of expected queries

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
    • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
    • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
    • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
    • Standard QE validation, with pre-merge tests unless stated otherwise.
    • Regression tests only (e.g. refactoring with no user-facing change).
    • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

@codecov
Copy link

codecov bot commented Oct 18, 2023

Codecov Report

Attention: 265 lines in your changes are missing coverage. Please review.

Comparison is base (988780d) 58.75% compared to head (a09bdfe) 57.89%.
Report is 2 commits behind head on main.

Files Patch % Lines
web/src/components/netflow-traffic.tsx 65.92% 60 Missing and 1 partial ⚠️
pkg/loki/topology_query.go 53.16% 33 Missing and 4 partials ⚠️
...components/query-summary/metrics-query-summary.tsx 57.14% 15 Missing and 9 partials ⚠️
...c/components/netflow-overview/netflow-overview.tsx 83.18% 10 Missing and 9 partials ⚠️
web/src/utils/metrics.ts 51.61% 14 Missing and 1 partial ⚠️
pkg/loki/flow_query.go 0.00% 14 Missing ⚠️
web/src/components/metrics/metrics-graph-total.tsx 65.00% 9 Missing and 5 partials ⚠️
...eb/src/components/netflow-overview/panel-kebab.tsx 65.00% 13 Missing and 1 partial ⚠️
web/src/components/metrics/metrics-donut.tsx 47.36% 7 Missing and 3 partials ⚠️
pkg/handler/validation.go 35.71% 9 Missing ⚠️
... and 14 more
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     
Flag Coverage Δ
uitests 59.22% <67.78%> (+0.47%) ⬆️
unittests 54.22% <45.21%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jpinsonneau
Copy link
Contributor Author

@jotak & @OlivierCazade could you please take a look at this draft so we can validate the approach ?
I would like to confirm this approach fits our needs and is not too heavy to maintain.
If you have a lighter alternative in mind please let me know 😃

Thanks !

@jotak jotak added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Oct 31, 2023
@github-actions
Copy link

New image:
quay.io/netobserv/network-observability-console-plugin:6fc9562

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

@jotak jotak changed the title NETOBSERV-1227 Max / P90 / P99 graphs NETOBSERV-1227: Max / P90 / P99 graphs Oct 31, 2023
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Oct 31, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@jotak
Copy link
Member

jotak commented Oct 31, 2023

Hmm in fact I was not thinking something that generic, as an approach. I think we need to distinguish two kinds of metrics:

  • counter-based metrics, such as our bytes/packet counters, that can be summed and which we compute rates on. For these metrics, on a given interval we don't "miss" data in the visualisation, since everything gets added to the counter.
  • ponctual measurements like latencies, that cannot be summed <= it's on these ones only that we want stats, because in a given interval we cannot represent all the variety of what we've got (low latencies, high latencies and their distribution) so we need stats like min/max/percentiles /...

So I think we should restrict these new charts to only latencies (RTT and DNS)

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Nov 2, 2023
@jpinsonneau
Copy link
Contributor Author

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.
ae9bcf5

image
image

@jotak jotak added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Nov 6, 2023
Copy link

github-actions bot commented Nov 6, 2023

New image:
quay.io/netobserv/network-observability-console-plugin:154f5c8

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

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 7, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

These changes will also fix NETOBSERV-1388

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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 jpinsonneau changed the title NETOBSERV-1227: Max / P90 / P99 graphs NETOBSERV-1227 NETOBSERV-1388: Max / P90 / P99 graphs Nov 7, 2023
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 7, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

These changes will also fix NETOBSERV-1388

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Nov 7, 2023
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 9, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

These changes will also fix NETOBSERV-1388

Dependencies

Based on #405

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 9, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

These changes will also fix NETOBSERV-1388

Dependencies

Based on #405

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 10, 2023

@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:

Description

  • min
  • max
  • P90
  • P99
  • choose defaults for each metric
  • topology
  • update testing

As we are getting a lots of graphs it would be cool to consider https://issues.redhat.com/browse/NETOBSERV-267 work on popups.

These changes will also fix NETOBSERV-1388

Dependencies

Based on #405
Blocked by #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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 10, 2023

@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:

Description

Add functions for time based metrics (DNS Latency / RTT):

  • min
  • max
  • P90
  • P99

Related changes:

  • refactor of overview page / graphs
  • new metrics on topology labels
  • query summary

These changes will also fix NETOBSERV-1388

Dependencies

Based on #405
Blocked by #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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 10, 2023

@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:

Description

Add functions for time based metrics (DNS Latency / RTT):

  • min
  • max
  • P90
  • P99

Related changes:

  • refactor of overview page / graphs
  • new metrics on topology labels
  • query summary

These changes will also fix NETOBSERV-1388

Dependencies

Based on #405
Blocked by #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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@Amoghrd
Copy link
Contributor

Amoghrd commented Nov 21, 2023

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved QE has approved this pull request label Nov 21, 2023
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 21, 2023

@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:

Description

Add functions for time based metrics (DNS Latency / RTT):

  • min
  • max
  • P90
  • P99

Related changes:

  • refactor of overview page / graphs
  • new metrics on topology labels
  • query summary
  • improved testing using a list of expected queries

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.

  • Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
  • Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
  • Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
  • Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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.

@jotak jotak added ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. and removed ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. labels Dec 5, 2023
Copy link

github-actions bot commented Dec 5, 2023

New image:
quay.io/netobserv/network-observability-console-plugin:9c09670

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

@jotak
Copy link
Member

jotak commented Dec 5, 2023

In topology when setting edge labels to DNS latencies, showing avg, max or p99 works but showing min or p90 doesn't:
image
I don't see any error in the console...

@jotak
Copy link
Member

jotak commented Dec 5, 2023

In topology side panel, I guess we should filter-out 0ms latencies prior to any calculation:
image
In this screenshot, it seems clear that lack of measurements show 0ms latencies and they are pulling down the averages as 0.1ms, 0.05ms or 0.5ms whereas I believe all averages on that capture should be 1ms

(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.

@jotak
Copy link
Member

jotak commented Dec 5, 2023

done with the review, I've found just 2 issues, after that it's lgtm, nice work!

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Dec 6, 2023
@jpinsonneau
Copy link
Contributor Author

Thanks for your feedback @jotak !

It seems indeed that DnsLatencyMs contains zeros which was not expected:

  "DnsErrno": 0,
  "DnsFlags": 34048,
  "DnsFlagsResponseCode": "NoError",
  "DnsId": 64587,
  "DnsLatencyMs": 0,

That's why the graph were showing zeros on bottomk min_over_time queries. We should investigate why we get these zeros. In between I've added a filter on query side to ensure we get non zero DnsLatency as:

|~`"DnsLatencyMs`!~`DnsLatencyMs%22:0[,}]`

Also skipped the normalization for dns & rtt queries and forced n/a label where values are not available.

972c7a5

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.

Could you please create a followup for this ? I'm open to any suggestions here

@jpinsonneau jpinsonneau added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Dec 7, 2023
Copy link

github-actions bot commented Dec 7, 2023

New image:
quay.io/netobserv/network-observability-console-plugin:d97e766

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

@Amoghrd
Copy link
Contributor

Amoghrd commented Dec 7, 2023

@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

@jpinsonneau
Copy link
Contributor Author

@jpinsonneau I still see the hole next to donut graphs, is that going to be fixed in another PR or in this itself?

This PR is not solving that yet. I was waiting for a decision in that thread:
https://redhat-internal.slack.com/archives/C02939DP5L5/p1701778618284139

I'm fine merging as is and doing a followup if we are not fixed yet 😉

@github-actions github-actions bot removed the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Dec 8, 2023
@jpinsonneau
Copy link
Contributor Author

@Amoghrd @jotak I've made the overview cards more responsive:
a09bdfe

image
image
image

That rely on css so every case is manage here

@Amoghrd
Copy link
Contributor

Amoghrd commented Dec 8, 2023

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. label Dec 8, 2023
Copy link

github-actions bot commented Dec 8, 2023

New image:
quay.io/netobserv/network-observability-console-plugin:81e04ef

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

Copy link
Member

@jotak jotak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link

openshift-ci bot commented Dec 11, 2023

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 1d3b420 into netobserv:main Dec 11, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/valid-reference lgtm ok-to-test To set manually when a PR is safe to test. Triggers image build on PR. qe-approved QE has approved this pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants