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.

Sign up for GitHub

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

Jump to bottom

Reporting periodic jobs failures to slack channel after number of consequent failures #32687

Closed
Sunnatillo opened this issue May 31, 2024 · 2 comments
Closed

Reporting periodic jobs failures to slack channel after number of consequent failures #32687

Sunnatillo opened this issue May 31, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@Sunnatillo
Copy link
Contributor

What would you like to be added:
We would like to add a Slack reporter for failed jobs to our cluster-api Slack channel. However, we are concerned about the potential for excessive notifications, as every failure would generate a message in the channel. It would be beneficial to implement a parameter similar to testgrid-num-failures-to-alert:5 for Slack reporters. Currently, this parameter only works for email notifications

Why is this needed:
To manage the frequency of Slack notifications by only sending alerts after a specified number of failures. This will reduce noise and prevent the Slack channel from becoming overwhelmed with failure messages.
@Sunnatillo Sunnatillo added the kind/feature Categorizes issue or PR as related to a new feature. label May 31, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 31, 2024
@Sunnatillo Sunnatillo changed the title Reporting periodic jobs failures to slack channel after number of consequent failures failures Reporting periodic jobs failures to slack channel after number of consequent failures Jun 3, 2024
@Sunnatillo Sunnatillo mentioned this issue Jun 3, 2024
Closed
@Aaina26
Copy link

Aaina26 commented Jun 12, 2024

/sig contributor-experience

@k8s-ci-robot k8s-ci-robot added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 12, 2024
@MadhavJivrajani MadhavJivrajani mentioned this issue Jun 14, 2024
Open
@MadhavJivrajani
Copy link
Contributor

Migrated issue: kubernetes-sigs/prow#195

@MadhavJivrajani MadhavJivrajani closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@MadhavJivrajani @k8s-ci-robot @Sunnatillo @Aaina26