-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[alerting] disable status reporting for now #116717
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
Conversation
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
|
The overall CI time is currently unchanged, but look at these individual step timing improvements (in minutes). This will be huge when I go to rebalance/split the ci groups. I had also been struggling with why the CI group timings fluctuated so much between runs sometimes, and I bet this will fix that as well. |
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
mikecote
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
💔 Backport failedThe backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
Co-authored-by: spalger <spalger@users.noreply.github.com>
Temporary mitigation for #116714
From what we can tell the alerting status isn't actually necessary for the plugin to operation successfully, and is only harming DX/UX as described in #116714, so this is an attempt to disable status reporting for now until a better long term solution can be determined with the Alerting team.