You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can one reproduce the bug?
Steps to reproduce the behavior:
Go to Alerting
Select Create Monitor
Select "Per query monitor" + "Anomaly detector"
Select an existing detector
See error
Repeat with "Remove Trigger" + "Add Trigger"
What is the expected behavior?
Should be possible to create a trigger on a AD feature
What is your host/environment?
OS: Macos 15x
Version 2.17.1
Plugins:
alerting-dashboards@2.17.1.0
anomaly-detection-dasbhoards@2.17.1.0
Do you have any additional context?
Im new to the plugin source code and need confirmation before working on a PR.
commit 9c4dfb0
changed the query schema from schema.any() to query: createValidateQuerySchema(dataSourceEnabled)
now the /.../startTime&endTime do not seem to be allowed.
All of the following fixes the issue and its possible to create a AD trigger
removing the validator
schema.any()
a schema loosely based on the observed query works
What is the bug?
It's not possible to create a trigger for an AD monitor the UI shows an error "Failed to Load..." while the network tab shows BadRequest on http://ose-dashboards:5603/api/alerting/detectors/u5gchpIBOU-wiD8XajaL/results?startTime=1728380244166&endTime=1728985044167&preview=true
{
"statusCode": 400,
"error": "Bad Request",
"message": "[request query.startTime]: definition for this key is missing"
}
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
Should be possible to create a trigger on a AD feature
What is your host/environment?
Plugins:
Do you have any additional context?
Im new to the plugin source code and need confirmation before working on a PR.
commit 9c4dfb0
changed the query schema from
schema.any()
toquery: createValidateQuerySchema(dataSourceEnabled)
now the
/.../startTime&endTime
do not seem to be allowed.All of the following fixes the issue and its possible to create a AD trigger
This does not seem to be #149
as I have tried with detectors having enough results.
The text was updated successfully, but these errors were encountered: