1. Proposed title of this feature request

>> Request for Feature Enhancement by Return Codes

3. What is the nature and description of the request?

>> Current Insights Ansible Automation Platform show failures - but not their reasons.
but this way of work is not effective in big service companies. How user should investigate and fix thousands of unsuccessful executions?

The subject of RFE is to enhance the official Ansible solution by the following elements:

• Ansible Role/Module for a population of Return Codes into Insights Ansible Automation Platform
• Guidelines on how to generate Return Codes from Playbooks (how to leverage mentioned Ansible Role/Module)
• Enhancement of Insights Ansible Automation Platform by processing and visualization of metrics based on Return Codes.

NOTE - Cu has a working solution for which is currently used for hundreds of customers. And cu is willing to show Red Hat how it works.

4. Why does the customer need this? (List the business requirements here)

>> To investigate and fix thousands of unsuccessful executions effectively.

5. How would the customer like to achieve this? (List the functional requirements here)

>> The subject of RFE is to enhance the official Ansible solution by the following elements:

• Ansible Role/Module for a population of Return Codes into Insights Ansible Automation Platform
• Guidelines on how to generate Return Codes from Playbooks (how to leverage mentioned Ansible Role/Module)
• Enhancement of Insights Ansible Automation Platform by processing and visualization of metrics based on Return Codes.

PFA document shared by the customer to understand the customers