[Bug]: Anomaly Advisor tab bug
Closed this issue · 4 comments
Bug description
- When I highlight a timeframe there is no loading indicator, and if the space has a lot of nodes the feature seems like it does not work
- When I highlight a timeframe the prompt
You haven't highlighted any timeframe yet.
does not change - Once the Anomaly Advisor eventually runs, if I click on a chart from the right column, the
You haven't highlighted any timeframe yet.
modal is hiding half the chart.
Expected behavior
- There should be an indication that the feature actually processes something.
- The prompt should indicate that I have indeed highlighted something, or vanish all-together.
- The bug should not be present
Steps to reproduce
- just use the feature
Screenshots
- I have highlighted a timeframe and nothing seems to happen. If I wait X amount of time it might bring results.
- Take a look at the grey top prompt, it says that I got no timeframe highlighted
Error Logs
No response
Desktop
Chrome, but not important I think
Additional context
No response
Similar to #819, but this exposes some different issues with the tab, so not a duplicate.
There should be an indication that the feature actually processes something.
This point was working in the past with some animation, just sharing that this is something we can do Surface a component that shows the progress when a transaction is initiated from the FE #4467
some feedback on this ticket
- When I highlight a timeframe there is no loading indicator, and if the space has a lot of nodes the feature seems like it does not work
- When I highlight a timeframe the prompt You haven't highlighted any timeframe yet. does not change
@kapantzak already fixed the above two points and this is released on Production
- Once the Anomaly Advisor eventually runs, if I click on a chart from the right column, the You haven't highlighted any timeframe yet. modal is hiding half the chart.
for this 3rd one the div is always there (sticky position to the top), to not go into a lot of work to change this behaviour the suggestion is to change the message displayed there to what it was before
Anomalous metrics in the selected timeframe sorted from most anomalous to least.
this is now fixed