Background

Automation Analytics currently has a report "Slow hosts by job template" that identifies the slowest hosts in a given job template. What defines their slowness is the amount of time they take to run tasks in a playbook. If we could pinpoint the exact task(s) that take a long time to execute on these slow hosts compared to the other peer hosts then that would be valuable information. With this information, one could  potentially fix the slowness of a given task on a given host.

For example - Consider 4 hosts - host1, host2, host3 and host4 for a given job template. These hosts run a task to download a python package from the internet using the 'get_url' module. host1, host2 and host3 consistently take around 10 seconds to download the file. host4 on the other hand, always records a high duration for this task close to 120 seconds or so. If we could identify that the task with the  'get_url' module that is responsible for downloading the python package on host4 is relatively slow compared to the peer hosts: host1, host2 and host3, we could check the network settings on host4 and possibly fix the slowness issue.

User Stories

As a user of Ansible Automation, I want the ability to identify the tasks that usually run slow on specific hosts in order to speed up the execution time of my playbooks and reduce the associated automation costs.

Supporting documentation

TBD

Ready-Ready

https://docs.google.com/document/d/1dBW492UfCR5JxUvcx6efjYP_ibCdiwGONS-sxDb_SPU/edit# 

Complete Ready-Ready checklist

Definition of Done

Should be agreed upon per team; add/remove/update to reflect:{}

• CI is running, tests are automated and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• DEV downstream build attached to advisory
• QE - Test plans documented and attached to epic (or link to source)
• QE - automated tests merged and passing
• Docs - Downstream documentation is merged
• PM - all acceptance criteria are met (note: we want to start using the AC specific field, but please fill out below in the meantime)

Note: please also fill out the 'Acceptance Criteria' to indicate functional criteria aka scope, specific to this issue, that should be met in order to 'accept' the work to consider complete.