Skip to content
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

[Logs UI] Show category anomalies in anomaly table #64755

Closed
katrin-freihofner opened this issue Apr 29, 2020 · 2 comments · Fixed by #70982
Closed

[Logs UI] Show category anomalies in anomaly table #64755

katrin-freihofner opened this issue Apr 29, 2020 · 2 comments · Fixed by #70982
Assignees
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services v7.9.0
Milestone

Comments

@katrin-freihofner
Copy link
Contributor

katrin-freihofner commented Apr 29, 2020

⚠️ Depends on: #63671

The anomaly table should hold category and log rate anomalies:

table

The expandable rows for categories are very similar to what we currently have in the category tab. New are the stats, showing the expected and actual values.

Note:

  • Sort rows by anomaly score, descending by default

Design issue
Figma file

@katrin-freihofner katrin-freihofner added the Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services label Apr 29, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

@weltenwort
Copy link
Member

I wonder if we could make the "more messages in this category" more useful 🤔 What does "this category" refer to? Should we show the category patterns somewhere to fill it with meaning?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services v7.9.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants