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

[Monitoring] Fetch status once and change fetchStatus to support an array of clusters #91749

Merged

Conversation

chrisronline
Copy link
Contributor

Resolves #91722

@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Contributor

@igoristic igoristic left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@chrisronline chrisronline merged commit a558920 into elastic:master Feb 18, 2021
@chrisronline chrisronline deleted the monitoring/efficient_alert_status branch February 18, 2021 13:47
chrisronline added a commit that referenced this pull request Feb 18, 2021
…rray of clusters (#91749) (#91840)

* Fetch status once and change fetchStatus to support an array of clusters

* Update test
chrisronline added a commit to chrisronline/kibana that referenced this pull request Mar 25, 2021
…rray of clusters (elastic#91749)

* Fetch status once and change fetchStatus to support an array of clusters

* Update test
chrisronline added a commit that referenced this pull request Mar 25, 2021
…rray of clusters (#91749) (#95409)

* Fetch status once and change fetchStatus to support an array of clusters

* Update test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Monitoring] Inefficient status fetching from alerts is causing long response times
4 participants