-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Conversation
[ML] Update snapshots [ML] Remove logs
[ML] Fix detector column name
…ions-enhancements # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
Pinging @elastic/ml-ui (:ml) |
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.
Great progress overall! I added some questions.
One more suggestion here since it applies to the PR overall:
aggregations
seemed to me like a very generic name for what we're now returning as part of the annotations results, it's quite a generic name and internal Elasticsearch concept. I wonder if we could rename it to somewhat more specific that reflects the type of data we're returning (types of events in this case so far)
x-pack/plugins/ml/public/application/components/annotations/annotation_flyout/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/ml/public/application/components/annotations/annotation_flyout/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/ml/public/application/components/annotations/annotation_flyout/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/ml/public/application/components/annotations/annotation_flyout/index.tsx
Outdated
Show resolved
Hide resolved
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
x-pack/plugins/ml/server/models/annotation_service/annotation.ts
Outdated
Show resolved
Hide resolved
Might not be directly related to the changes in this PR, but the message here should be altered to say something like |
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
[ML] Refactor ANNOTATION_EVENT_USER & minor fixes
…ions-enhancements # Conflicts: # x-pack/plugins/ml/public/application/explorer/actions/load_explorer_data.ts # x-pack/plugins/ml/public/application/explorer/explorer.js # x-pack/plugins/ml/public/application/explorer/explorer_utils.js # x-pack/plugins/ml/public/application/explorer/reducers/explorer_reducer/reducer.ts # x-pack/plugins/ml/public/application/explorer/reducers/explorer_reducer/state.ts
- Add partitioning fields & detector to annotation flyout - Fix annotation layout overlay in AE - Add direct link to SMV with partitioning fields in detector - Update width for partitioning columns - Show all partitioning columns for both SMV and AE - Fix bug with annotation not editable by finding the original annotation
- When updating system generated annotation, persist the `event` field
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Outdated
Show resolved
Hide resolved
.../plugins/ml/public/application/components/annotations/annotations_table/annotations_table.js
Show resolved
Hide resolved
@elasticmachine merge upstream |
@elasticmachine merge upstream |
…ions-enhancements # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…ions-enhancements # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…ions-enhancements # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
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 changes and LGTM
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.
LGTM
…ions-enhancements # Conflicts: # x-pack/plugins/ml/server/models/results_service/get_partition_fields_values.ts
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
This PR brings several enhancements from meta issue #69538
UI
EuiPanel
If there's no user annotations, it will show user (0) selected
Increase the width for
Event
so that it can show the full messageAdd search bar
Add ability to filter annotations by partitioning field name/values
Filter the annotations table in the Single Metric Viewer to show annotations for the selected partitioning fields only
Add checkbox in the creation fly-out to indicate whether or not the annotation applies to only that partition or the whole job. This will record the following properties if they exist in the
chartProperties
:Service
event
asuser
when a user creates an annotation (right now the event is null/empty)Checklist
Delete any items that are not applicable to this PR.