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

[Response Ops] Using data view service to fetch data views #131330

Merged
merged 4 commits into from
May 6, 2022

Conversation

ymao1
Copy link
Contributor

@ymao1 ymao1 commented May 2, 2022

Resolves #129914

Summary

Using data view service to fetch index patterns instead of using the saved objects client directly. Previously, when using the saved objects client, we retrieved 1000 data views at a time and paginated if the total number of matching data views exceeded 1000. The data views service does not provide the ability to specify page number so functionality for this changes a bit as loadIndexPatterns will now only return up to 1000 matching data views. Discussed with the team and we felt that this should be sufficient, especially since the data views are filtered based on user input.

To Verify

Verify that selecting index pattern for Index Threshold and ES Query rule type still work as expected. Also verify that selecting index pattern for ES Index connector type works as expected.

Checklist

@ymao1 ymao1 self-assigned this May 2, 2022
@ymao1 ymao1 added release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types v8.3.0 and removed Feature:Alerting/RuleTypes Issues related to specific Alerting Rules Types labels May 2, 2022
@ymao1 ymao1 marked this pull request as ready for review May 2, 2022 16:13
@ymao1 ymao1 requested a review from a team as a code owner May 2, 2022 16:13
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@ymao1
Copy link
Contributor Author

ymao1 commented May 3, 2022

@elasticmachine merge upstream

Copy link
Contributor

@mikecote mikecote left a comment

Choose a reason for hiding this comment

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

Changes LGTM! Tested locally and it works 👍

@ymao1
Copy link
Contributor Author

ymao1 commented May 5, 2022

@elasticmachine merge upstream

@ymao1
Copy link
Contributor Author

ymao1 commented May 6, 2022

@elasticmachine merge upstream

Copy link
Contributor

@ersin-erdal ersin-erdal left a comment

Choose a reason for hiding this comment

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

spring cleaning LGTM :)

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
triggersActionsUi 724.0KB 724.0KB -10.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
triggersActionsUi 100.5KB 100.2KB -343.0B

History

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

cc @ymao1

@ymao1 ymao1 merged commit 43c4134 into elastic:main May 6, 2022
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label May 6, 2022
@ymao1 ymao1 deleted the alerting/use-index-pattern-service branch May 6, 2022 13:12
kertal pushed a commit to kertal/kibana that referenced this pull request May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Alerting] Use index pattern service to load index patterns
6 participants