-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
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
[BUG] exception instead of proper error #126
Comments
@skkosuri-amzn What is the state of this issue? Alerting was marked feature complete per #182 |
This got moved out of 1.2. Removed the tag. |
To add some info here when we revisit the issue, this happened because the
We do correctly assert on a non-null Monitor name when the data class is being returned after the parsing has completed, which would have given us a more useful message if it had failed:
However because the lateinit var was never initialized, we hit that exception first. So we should change that to
|
Getting an exception when trying to update a monitor with copy-pasted data from
GET _opendistro/_alerting/monitors/<monitor_id>
:Input request body doesn't conform to spec, but user shouldn't be confused by irrelevant error. Instead, a proper error should be emitted like "supplied data is incorrect, check docs" or whatever.
ver
opendistro-alerting-1.13.1.0-1.noarch
Thanks.
The text was updated successfully, but these errors were encountered: