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-1313 enable feature gated panels by default #402

Merged
merged 1 commit into from
Oct 4, 2023

Conversation

jpinsonneau
Copy link
Contributor

@jpinsonneau jpinsonneau commented Sep 22, 2023

Description

Show DNS & RTT panels by default (when feature enabled)
Backport: #403

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

@codecov
Copy link

codecov bot commented Sep 22, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (82c4ac9) 57.80% compared to head (2bdc792) 57.47%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #402      +/-   ##
==========================================
- Coverage   57.80%   57.47%   -0.33%     
==========================================
  Files         167      168       +1     
  Lines        7871     7944      +73     
  Branches      970      970              
==========================================
+ Hits         4550     4566      +16     
- Misses       3042     3099      +57     
  Partials      279      279              
Flag Coverage Δ
uitests 58.43% <ø> (+0.27%) ⬆️
unittests 54.79% <ø> (-1.98%) ⬇️

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

Files Coverage Δ
web/src/utils/overview-panels.ts 75.86% <ø> (+6.89%) ⬆️

... and 5 files with indirect coverage changes

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

{ id: 'top_dns_rcode_bar_total', isSelected: false },
{ id: 'top_avg_rtt_donut', isSelected: false },
{ id: 'top_avg_rtt_line', isSelected: false }
{ id: 'top_avg_dns_latency_donut', isSelected: true },
Copy link
Member

Choose a reason for hiding this comment

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

should we be more selective and not display them all by default? E.g. show donuts, which are more lightweight, than line/bar charts for the same metric ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I guess it's more a matter of advertising what's available here more that anything don't you think ?

That selection is kept in cache so this will affect only the first time until the user actually configure the panels (or get new panels not yet assigned from new feature / operator update).

@Amoghrd
Copy link
Contributor

Amoghrd commented Sep 28, 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 Sep 28, 2023
@github-actions
Copy link

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

It will expire after two weeks.

To deploy this build, run from the operator repo, assuming the operator is running:

USER=netobserv VERSION=d420a1e make set-plugin-image

@Amoghrd
Copy link
Contributor

Amoghrd commented Sep 28, 2023

@jpinsonneau This PR seems to be breaking the consolePlugin. I am hitting the below error as soon as I patch the above image.
Screenshot 2023-09-28 at 2 31 04 PM

@jpinsonneau
Copy link
Contributor Author

@jpinsonneau This PR seems to be breaking the consolePlugin. I am hitting the below error as soon as I patch the above image. Screenshot 2023-09-28 at 2 31 04 PM

Just tried on OCP 4.13.13 and it works fine 🤔 Which version did you tried ?

Your react error is pointing #306

Element type is invalid. Received a promise that resolves to: [missing argument]. Lazy element type must resolve to a class or function.[missing argument]

Which is not enough to find where it comes from 😞

@Amoghrd
Copy link
Contributor

Amoghrd commented Oct 2, 2023

@jpinsonneau Yeah the image works fine, think I was using older release of operator before which may have led to that error idk. Anyways, the DNS panels are seen on default but when I click on RestoreDefaults it removed those panels which is not the case for PacketDrop which dont go away upon click.

@jpinsonneau
Copy link
Contributor Author

@jpinsonneau Yeah the image works fine, think I was using older release of operator before which may have led to that error idk. Anyways, the DNS panels are seen on default but when I click on RestoreDefaults it removed those panels which is not the case for PacketDrop which dont go away upon click.

I think you are still facing some cache issue here:
Screencast from 2023-10-03 09-51-33.webm

I double checked the code and confirm this is the only place where panels defaults are set.

Could you please clear your browser cache before giving another try ? Or just change browser to ensure no cache is there.
Local storage is not supposed to impact this as the defaults are not saved there. However, if nothing works, please give another try cleaning it.

On my side I will investigate to get rid of all of these cache issues.

@Amoghrd
Copy link
Contributor

Amoghrd commented Oct 3, 2023

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved QE has approved this pull request label Oct 3, 2023
@jpinsonneau
Copy link
Contributor Author

/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 4, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpinsonneau

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-ci openshift-ci bot added the approved label Oct 4, 2023
@openshift-ci openshift-ci bot merged commit 62bdb9d into netobserv:main Oct 4, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved 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.

None yet

3 participants