forked from elastic/kibana
-
Notifications
You must be signed in to change notification settings - Fork 0
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
add ilm explain api #5
Merged
angorayc
merged 2 commits into
andrew-goldstein:data-quality-dashboard
from
angorayc:ilm-api
Jan 7, 2023
Merged
add ilm explain api #5
angorayc
merged 2 commits into
andrew-goldstein:data-quality-dashboard
from
angorayc:ilm-api
Jan 7, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrew-goldstein
approved these changes
Jan 5, 2023
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.
Thanks @angorayc for implementing this API 🙏
✅ desk tested locally
LGTM 🚀
andrew-goldstein
added a commit
that referenced
this pull request
May 10, 2023
…k and New chat button #5 - adds the useSecurityAssistantQuery hook - adds a `New chat` button that renders a query in a popover
andrew-goldstein
added a commit
that referenced
this pull request
Aug 28, 2023
``` Test Failures [job] [logs] Jest Integration Tests #5 / checking migration metadata changes on all registered SO types detecting migration related changes in registered types [job] [logs] Jest Integration Tests elastic#6 / incompatible_cluster_routing_allocation retries the INIT action with a descriptive message when cluster settings are incompatible [job] [logs] Jest Integration Tests elastic#6 / migrating from 7.3.0-xpack which used v1 migrations copies all the document of the previous index to the new one [job] [logs] Jest Integration Tests elastic#6 / migrating from 7.3.0-xpack which used v1 migrations creates the new index and the correct aliases [job] [logs] Jest Integration Tests elastic#6 / migrating from 7.3.0-xpack which used v1 migrations migrates the documents to the highest version [job] [logs] Jest Integration Tests elastic#6 / migration v2 - read batch size does not reduce the read batchSize in half if no batches exceeded maxReadBatchSizeBytes [job] [logs] Jest Integration Tests elastic#6 / migration v2 - read batch size reduces the read batchSize in half if a batch exceeds maxReadBatchSizeBytes [job] [logs] Jest Integration Tests #5 / migration v2 fails with a descriptive message when maxBatchSizeBytes exceeds ES http.max_content_length [job] [logs] Jest Integration Tests #5 / migration v2 with corrupt saved object documents collects corrupt saved object documents across batches [job] [logs] Jest Integration Tests elastic#6 / SO default search fields make sure management types have the correct mappings for default search fields [job] [logs] Jest Integration Tests elastic#6 / SO type registrations does not remove types from registrations without updating excludeOnUpgradeQuery [job] [logs] Jest Integration Tests #4 / split .kibana index into multiple system indices when migrating from a legacy version performs v1 migration and then relocates saved objects into different indices, depending on their types [job] [logs] Jest Integration Tests #4 / split .kibana index into multiple system indices when multiple Kibana migrators run in parallel correctly migrates 7.7.2_xpack_100k_obj.zip archive [job] [logs] Jest Integration Tests elastic#6 / when splitting .kibana into multiple indices and one clone fails after resolving the problem and retrying the migration completes successfully ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is a part of https://github.com/elastic/security-team/issues/5578
Request:
example: GET /internal/data_quality/ilm_explain/auditbeat-*
Response:
Checklist
Delete any items that are not applicable to this PR.