Skip to content
This repository was archived by the owner on Dec 5, 2023. It is now read-only.

Display cluster name#10

Merged
openshift-ci[bot] merged 1 commit intoopenshift:mainfrom
anispate:display_cluster_name
Jul 7, 2022
Merged

Display cluster name#10
openshift-ci[bot] merged 1 commit intoopenshift:mainfrom
anispate:display_cluster_name

Conversation

@anispate
Copy link
Contributor

Adding an option to display the cluster name for the question "Which alerts fire more than once per on-call shift (in the same cluster)?"

It will print the cluster name rather than the cluster ID

@openshift-ci openshift-ci bot requested review from aweiteka and bdematte June 27, 2022 03:50
@abyrne55 abyrne55 changed the title Display cluster name [WIP] Display cluster name Jun 28, 2022
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 28, 2022
@aweiteka
Copy link

@anispate could you add a screenshot that demonstrates this UI change?

@anispate
Copy link
Contributor Author

image

Hi Aaron,

PFA to view the image for the UI Change

@fahlmant
Copy link

@anispate Looks like the style test is failing

@aweiteka
Copy link

Looks good. FWIW, the "osd-" string prefix not technically part of the cluster name. I'm not sure if it's worth the effort to remove it.

@fahlmant
Copy link

I don't think Zabbix is the correct title for this either

@abyrne55
Copy link
Contributor

/retest

models.py Outdated
from sqlalchemy.orm import relationship
from sqlalchemy.sql import func as sqlfunc
from sqlalchemy.ext.hybrid import hybrid_property
from sqlalchemy import func
Copy link
Contributor

Choose a reason for hiding this comment

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

This was my bad for telling you to add this import, as I didn't realize we already imported func on line 23 (we just rename it to sqlfunc). Could you remove this import and replace your use of func on line 174 with sqlfunc?

Once that's done, remove the [WIP] from this PR's title, and it'll be ready to review.

@abyrne55
Copy link
Contributor

abyrne55 commented Jul 1, 2022

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jul 1, 2022
@fahlmant
Copy link

fahlmant commented Jul 1, 2022

@anispate Can you please squash the commits?

@anispate anispate force-pushed the display_cluster_name branch from d8dfcaa to 719b284 Compare July 6, 2022 17:37
@anispate anispate changed the title [WIP] Display cluster name Display cluster name Jul 6, 2022
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 6, 2022
questions.py Outdated
"Which alerts fire more than once per on-call shift (in the same cluster)?"
)
self._column_names = ["cluster", "name", "namespace", "urgency", "flaps"]
self._column_names = ["ID", "Cluster", "Alert", "namespace", "urgency", "flaps"]
Copy link

Choose a reason for hiding this comment

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

nit: could we stick to the same casing for all column names? e.g. "namespace", "urgency", "flaps" are all lowercase.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay thats a good point. Let me make that change

@ritmun
Copy link

ritmun commented Jul 7, 2022

Left one nit. One more nit: Should we call the column "service" instead of "Cluster name", since that is honestly what we're using? Sometimes the service maybe dead man's snitch/Zabbix which isn't really a cluster name.

@ritmun
Copy link

ritmun commented Jul 7, 2022

/lgtm

@anispate anispate force-pushed the display_cluster_name branch from 48c9505 to 7ae5d6a Compare July 7, 2022 15:17
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

@anispate: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

Copy link
Contributor

@abyrne55 abyrne55 left a comment

Choose a reason for hiding this comment

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

/approve

Tested locally and confirmed proper operation. Nice work, @anispate, and thanks for the PR!

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abyrne55, anispate

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2022
@openshift-ci openshift-ci bot merged commit ca0166f into openshift:main Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants