Mohammad Qureshi
Mohammad Qureshi
Adding a note here that if this enhancement ends up adding a condition check where the sweeper is enabled or disabled for jobs ([similar to what Alerting currently does](https://github.com/opendistro-for-elasticsearch/alerting/blob/8daf9e64ccfd4219441002a821a2bb48bbeeaaf9/core/src/main/kotlin/com/amazon/opendistroforelasticsearch/alerting/core/JobSweeper.kt#L120)) we...
This API was disabled in https://github.com/opensearch-project/notifications/pull/420 for now. This issue will be revisited along with the reintroduction of that API.
Tagging this as a conversation for `3.0` as it might break any webhooks that are currently hitting `localhost`. We shouldn't prevent users from removing this value on personal clusters should...
This issue seems to be due to some bad requests throwing `500`s instead of `4xx` when having parsing issues. This doesn't seem to be just a Notifications issue, it can...
@dblock This was encountered for the Alerting OpenSearch repo. We don't have insight into the branch protection rules in the `Settings` but after I pushed the dev branch `bucket-level-alerting-dev` into...
Some related issues: #57 #99. After triage, we can include the exact difference in supported `ctx` variables and those included in the documentation to scope out the changes needed.
Including #50 here as well since the documentation shows `ctx.monitor.inputs.search.query` which I believe is what that user was looking for but is not available in `ctx`.
Here is a breakdown of all the `ctx` variables and any discrepancies between their inclusion in documentation, current support and intention to support. Making the changes themselves are straightforward, we'll...
After some discussion, the table above now reflects the current state of what is planned to be supported and what isn't. There will also need to be a separate PR...
Neither the PR (https://github.com/opensearch-project/alerting/pull/504) nor the documentation changes have been made for this issue @praveensameneni. The PR will need to be rebased and merged and we need the documentation changes...