Surya Sashank Nistala
Surya Sashank Nistala
@gaiksaya The integration tests are failing because of `WarningFailureException` This arises when there are warnings (not errors) in code execution.
https://github.com/opendistro-for-elasticsearch/asynchronous-search/pull/39/files This should fix the issue... we removed deprecated api calls made in the tests
@lehmat are you able to edit the alerting settings as Admin user after converting to SAML?
@zil1 I see that you have raised a concern for "Per document monitor" in specific. For per doc monitors, have you checked out [Document Findings](https://opensearch.org/docs/latest/monitoring-plugins/alerting/monitors/#document-findings)? In `ctx`, we have the...
@rblcoder Currently each trigger type is associated to specifc monitor type. We encourage you to raise a PR to add support for such an API if you have a use...
**We can invoke `ExecuteMonitorAction` in runJob flow in job scheduler**
will explore how I can factor in available free memory at that point in time and we can decide on the acceptable fraction of the heap size and if the...
@sbcd90 Should we also add another condition to do batching of percolate query based on num docs and limit to 100k per search at max along with the memory limit....
Closing in favor of smaller PRs
- What is the scope here - will AD plugin and security analytics plugin also become cross-cluster compliant if we add support in Alerting plugin? - What about cluster metrics...