Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[ML] Anomaly Detection: Annotations enhancements #70198
[ML] Anomaly Detection: Annotations enhancements #70198
Changes from 9 commits
ff3f180
9ffddf3
e517350
20ce417
2501b5f
e0ce77f
f96e042
4877939
ffd474a
2ee31d4
36a5a44
def94c3
bbdbec6
55aa5c8
a56fa66
07e396d
002eaf3
5b6249d
010c096
0d945fa
b69be14
1f2684d
e57889f
dfe3950
aa98817
02024e5
0e24cb3
687fed9
de5e991
fe58c7d
c06b83b
4871783
ad7a947
00b6c88
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The interfaces defined here will be applicable for other types than annotations I'm sure, but till we hit that use case, probably makes sense to leave them defined in here. I had a quick look to see if I could find something similar in our existing types, and the Kibana data plugin, but couldn't find anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When editing a series level annotation, this checkbox should be initialized with the checked state. For me, it is normally opening unchecked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now checked on by default here 1f2684d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, if editing an existing series level annotation, if the user then unticks the 'apply to series' checkbox, we should clear the partitioning and detector index fields of the annotation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@qn895 , I'm not sure if this screenshot is still current. But I'm noticing the footer actions. The 'Delete' action should be next to the 'Update' button instead of even spacing between all buttons. You also do not need the cross next to 'Cancel'
For example... (checkmark not needed in your case)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested latest edits, and the partitioning and detector fields are now removed as expected if I untick the 'apply to series' checkbox when editing an annotation.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.