Skip to content

Conversation

@toepkerd
Copy link
Collaborator

@toepkerd toepkerd commented Nov 2, 2025

Description

Get Alerts and Alert Lifecycle

ITs depend on execute monitor functionality that has not yet been published, but they have been written: https://github.com/toepkerd/alerting/blob/ppl-main/alerting/src/test/kotlin/org/opensearch/alerting/alertsv2/AlertV2IndicesIT.kt

Related Issues

#1880

Check List

  • [Y] New functionality includes testing.
  • New functionality has been documented.
  • API changes companion pull request created.
  • [Y] Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

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.

Signed-off-by: Dennis Toepker <toepkerd@amazon.com>
Signed-off-by: Dennis Toepker <toepkerd@amazon.com>
val monitorV2Id: String?
val monitorV2Ids: List<String>?
val alertV2Ids: List<String>?
val boolQueryBuilder: BoolQueryBuilder?
Copy link
Member

@eirsep eirsep Nov 3, 2025

Choose a reason for hiding this comment

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

do we intend to support BoolQueryBuilder in API? user prolly wouldn't know Alert structure and this could be a security issue i reckon if user is able to query alerts by User fields,

import org.opensearch.index.query.BoolQueryBuilder
import java.io.IOException

class GetAlertsV2Request : ActionRequest {
Copy link
Member

Choose a reason for hiding this comment

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

shouldn't we also be implement xcontent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants