We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Today Alerting execution is not tracked by Opensearch task manager because it is executed as a Job Scheduler job.
This renders us without any control over long runnign monitor exceutions which we may want to cancel or abort
All operations in Opensearch are registerable in Opensearch framework A sample task looks like
retention_lease_background_sync NS5L3EYoSM2ED7Ivqq1snQ:993186 - transport 1706578387362 01:33:07 5.1h 10.212.107.51 5112ba5b511cfd4495
Alerting monitor execution scheduled by job schuedler should register a cancellable task
alerting/monitor/scheduled NS5L3EYoSM2ED7Ivqq1snQ:993186 - transport 1706578387362 01:33:07 1.5m 10.212.107.51 5112ba5b511cfd4495
task can contain details like monitor id to help with tracking which node is running the monitor.
The text was updated successfully, but these errors were encountered:
We can invoke ExecuteMonitorAction in runJob flow in job scheduler
ExecuteMonitorAction
Sorry, something went wrong.
No branches or pull requests
Today Alerting execution is not tracked by Opensearch task manager because it is executed as a Job Scheduler job.
This renders us without any control over long runnign monitor exceutions which we may want to cancel or abort
All operations in Opensearch are registerable in Opensearch framework
A sample task looks like
Alerting monitor execution scheduled by job schuedler should register a cancellable task
task can contain details like monitor id to help with tracking which node is running the monitor.
The text was updated successfully, but these errors were encountered: