-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] anomaly view cleanup #65046
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
looks nice and clean 🧹
So we don't want to link to the ML UI anymore? Or did you mean to say that the "Reconfigure job" button should be replaced? |
Very good question. I think it's probably more interesting to look at specific anomalies in ML. Besides that, I'm wondering if we can link somewhere meaningful - we are going to have categories and log rate anomalies there. |
True, there's no one link once we have multiple anomaly types in there. We already have per-row "Analyze in ML" links that depend on the specific anomaly type. Is there a downside to keeping the link until we're at the point that we're showing the anomalies from multiple jobs? |
I don't see one, I'm perfectly fine with keeping it for now. |
This ticket summarizes a cleanup of the Anomalies/Log rate tab.
This is dependent on the new anomaly table and setup flyout
Goal
The outcome of this ticket should look similar to this
Todos
Analyze in ML
button should be replaced to trigger the setup flyout ([Logs UI] Move ML job setup to flyout #64754)Please reach out anytime if something is unclear.
The text was updated successfully, but these errors were encountered: