-
Bug
-
Resolution: Done
-
Undefined
-
None
-
aa-latest
-
None
-
None
-
False
-
-
False
-
None
-
https://github.com/RedHatInsights/tower-analytics-frontend/pull/855, https://gitlab.cee.redhat.com/automation-analytics/automation-analytics-backend/-/merge_requests/509, https://gitlab.cee.redhat.com/automation-analytics/pdf-generator/-/merge_requests/117, https://github.com/RedHatInsights/tower-analytics-frontend/pull/902
-
Sprint ending Aug 10, 2022, Sprint ending Sept 7, 2022, Sprint ending Oct 5, 2022, Sprint ending Oct 27th, Sprint ending Nov 30, 2022, Sprint ending Dec 28, 2022
Report: Host anomalies by job template
- In the list, showing ID of a template serves no real purpose.
We should remove the ID and instead have the following columns that will add more insight to the report -- Template name
- Average duration per task
- Host count
- Slow hosts count
- The sorting seems to be broken. Tried sorting it by slow hosts count, host task count etc. It does not seem to work
- Pagination seems broken as well. In most other reports, we fetch 6 items at a time. Doesn't seem to be the case here. Also, clicking on next page basically shows the same contents as the first page.
- Lastly, the word "Anomaly" or "Anomalies" seems a bit extreme. We are currently singling out slow hosts in a template based on their average duration per task. Other than the 'duration' attribute, there is no other decision-making parameter being used. Therefore, just calling these hosts as "slow" is good enough. Hence, the report should be renamed to "Slow hosts by job template".
Note: The backend does refer to the slow host with the 'anomaly' attribute – it should have been referred to as 'slow_host' in the backend as well.
In the future, we could have more host properties available to us such as memory, cpu, vendor etc. Maybe then, the term 'Anomaly' might seem okay.
Question: Why was "Past 3 weeks" chosen as the default time window?
Report: Host anomaly run rate
- In the list, showing ID of a host serves no real purpose (same as the above report)
We should remove the ID and instead have the following columns that will add more insight to the report -- Host
- Host status
- Host Average duration per task
- Last referenced
- Slow (note the column name change from 'Anomalous' to 'Slow')
- There seems to be no pagination here. We could potentially have thousands of hosts, hence pagination would be necessary.
- Filtering: It looks like the 'Host Status' filter was left out for some reason. It is important to include that filter because, the user may want to find the slow hosts in a template based on their host status. For e.g. look for slowness in all 'ok' hosts or all 'changed' hosts
- The tooltip on the host seems incorrect (shows incorrect host status) and also confusing. Proposed tooltip text -
Host: HostXYZ Average duration per task: 10.2 Host status: changed Total tasks executed: 10 Last Referenced: 2022-07-25T11:45:45.008311 Slow: True
5. As mentioned above, the word "Anomaly" or "Anomalous" seems a bit extreme, considering that this report is only about slowness or slow performance of a host. Therefore, lets rename this report to "Slow hosts in a job template"
6. (Purely UX) When the scatter plot is sparsely populated, the white space in the chart gives an overly empty feel. In the plotly library, the background color of the scatter plot is a shade of gray, which is more pleasing to the eyes than the white color that we currently have (see attached html file: scatterplot_hosts.html)
ADDITIONAL ITEMS ADDED 08/30/2022:
- Round the Average duration per task and Host average duration per task up to 2 decimal places. So, 76.96 instead of 76.9572945 (I believe the Auto Calc does something like that, so you can refer that)
- In the kebab menu change 'Display only fast hosts' to 'Display only non-slow hosts'
- In src/Utilities/constants.ts, make sure that slow_host_view is set to 'templates_with_any_hosts' for the scatter plot report
- Add another column in the scatter plot report list for 'Total tasks executed'