-
Notifications
You must be signed in to change notification settings - Fork 90
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
[FEATURE ENHANCEMENT UX] Cross cluster search support in the OpenSearch alerting plugin #796
Labels
Comments
This was referenced Feb 5, 2024
cwperks
pushed a commit
to opensearch-project/security
that referenced
this issue
Feb 8, 2024
…alerting plugin feature #4027 (#4029) ### Description We added a new API to the alerting plugin to support enhancements to the UI ([link](https://github.com/opensearch-project/alerting/blob/main/alerting/src/main/kotlin/org/opensearch/alerting/action/GetRemoteIndexesAction.kt#L13)). The enhancements allow users to configure per query, and per bucket monitors that can query remote clusters via the UI. Previously, such monitors could only be configured using devtools/API commands. In addition, we added support for configuring cluster metrics monitors which can execute various API ([link to full list of supported API](https://opensearch.org/docs/latest/observing-your-data/alerting/per-cluster-metrics-monitors/#supported-apis)) against remote clusters. The new API is used by the frontend to also support creating these monitors via the UI. * Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation) * New experimental feature * Enhancement to existing features * Why these changes are required? * To include this API permission in the reserved role that's shipped with the default distribution of OpenSearch. * What is the old behavior before changes and new behavior after changes? * This API was not available before the experimental launch. With the experimental feature enabled, this API can be used to retrieve a list of connect remote clusters, the indexes/aliases on those clusters along with their health statuses, and optionally the mappings for those indexes. ### Issues Resolved opensearch-project/alerting-dashboards-plugin#796 Is this a backport? If so, please add backport PR # and/or commits # #4027 ### Testing Executed E2E tests with and without the experimental feature enabled to help ensure no regressions. ### Check List - [x] New functionality includes testing - [x] New functionality has been documented - [x] Commits are signed per the DCO using --signoff By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). --------- Signed-off-by: AWSHurneyt <hurneyt@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Currently the plug-in’s Per query, Per bucket, and Per document monitors are only able to query data sources on the local cluster.
What solution would you like?
We want to provide alerting capabilities for customers that need to query data across multiple clusters.
** UX Updates to plug-in interface **
Updates include changes to the Create monitor flow data source section:
If there are issues with remote cluster performance, the Preview and query performance accordion should automatically open once the service runs a query to display possible issues with the data sources selected:
![Screenshot 2023-11-03 at 2 08 18 PM](https://private-user-images.githubusercontent.com/111922174/281152315-da88e8f8-e76e-4f20-ab69-86d2a1b57ab7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ0NzA1NzksIm5iZiI6MTczNDQ3MDI3OSwicGF0aCI6Ii8xMTE5MjIxNzQvMjgxMTUyMzE1LWRhODhlOGY4LWU3NmUtNGYyMC1hYjY5LTg2ZDJhMWI1N2FiNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTIxN1QyMTE3NTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iOTJjMDNiNjQyOGUxOTA3ZDBhOTM2YzU4OTk2MDEzMzhkNDFlYTg1NGZjYjAwY2MwNjVlZjc5MTg1Zjg0YWEyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.crfUBHG1Ir8PsNzg0zntYnegXxuhBT2NAEKoI5I8Y0I)
If the customer continued with the monitor creation, a modal detailing impact on performance should launch giving users the option to tweak configurations:
![Screenshot 2023-11-03 at 2 08 26 PM](https://private-user-images.githubusercontent.com/111922174/281152420-730e1948-416a-4212-a66f-d22abab13e4e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ0NzA1NzksIm5iZiI6MTczNDQ3MDI3OSwicGF0aCI6Ii8xMTE5MjIxNzQvMjgxMTUyNDIwLTczMGUxOTQ4LTQxNmEtNDIxMi1hNjZmLWQyMmFiYWIxM2U0ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTIxN1QyMTE3NTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01ZmRkZGFkMTg3MTcwY2YyNDY2NWI5NWY2YTA3M2M3YTEyMzZhNzVjNTZhMTcyMTcxN2ZhY2I5ZDFmNWE1NDYyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.mtuzQ-jpwqmBKoSFmcRIa01qS3Ko2GVXodAuVRe3bYE)
Update to the Monitor details page includes:
The text was updated successfully, but these errors were encountered: