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

release-23.2: ui: remove duplicates of metrics on tooltip #113728

Merged
merged 1 commit into from Nov 7, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Nov 3, 2023

Backport 1/1 commits from #113710 on behalf of @maryliag.

/cc @cockroachdb/release


Fix #113701

When a cluster had several nodes, the metrics were being duplicate for each node on the charts.
This commits removes the duplicates, generating a single unique list of metrics.

Before (cluster with 4 nodes)
Screenshot 2023-11-02 at 4 35 04 PM

After (cluster with 4 nodes)
Screenshot 2023-11-02 at 4 39 01 PM

Release note (bug fix): Remove duplication of metrics on chart's tooltips.


Release justification: bug fix

Fix #113701

When a cluster had several nodes, the metrics were being
duplicate for each node on the charts.
This commits removes the duplicates, generating a single
unique list of metrics.

Release note (bug fix): Remove duplication of metrics on
chart's tooltips.
@blathers-crl blathers-crl bot requested a review from a team as a code owner November 3, 2023 02:03
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Nov 3, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.2-113710 branch from 600b13d to ca71cc9 Compare November 3, 2023 02:03
Copy link
Author

blathers-crl bot commented Nov 3, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL and one additional
    TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Nov 3, 2023
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@maryliag maryliag requested review from dhartunian and rafiss and removed request for sean-, abarganier and xinhaoz November 3, 2023 14:42
Copy link
Collaborator

@dhartunian dhartunian left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @maryliag)

@maryliag maryliag merged commit c9ed4dc into release-23.2 Nov 7, 2023
5 of 6 checks passed
@maryliag maryliag deleted the blathers/backport-release-23.2-113710 branch November 7, 2023 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants