Need ability to trace a job back to its launch source

What is the nature and description of the request?

External logging in AAP provides information about jobs and activity (and more). However, it doesn't provide a clear way to trace a job execution back to its source when launched by nested workflows.

For example, if you have the following workflows:

Workflow1: launch Workflow2
Workflow2: launch Job1

Given the job id for Job1 above,

• you can use the logs to determine the job id for Workflow2 by looking at the playbook_on_start event, which states the job id for Job1, and the parent job id for Worklow2
• however, you are unable to determine the job id for Workflow1 from the Workflow2 job id. There is no link between Workflow1 and Workflow2. 

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

There are Federal requirements for all financial institutions to track and prove who made what change on what system at what time. We are required to be able to track via logs who initiated a job in Ansible and all subsequent children jobs are run and what changes are made.

How would you like to achieve this? (List the functional requirements here)

If someone manually launches a workflow, there is an activity stream entry for `Activity Stream update entry for workflow_job` which includes the person who launched the job (actor), and the workflow job id.

If a workflow launches a workflow, there is the same activity stream entry for `Activity Stream update entry for workflow_job` which includes a "None" value for the person who launched the job (actor), and the workflow job id for the child workflow.

The proposal would be to replace "None" with something meaningful like "Workflow1-34453" ([Parent_workflow_name]-[parent_workflow_id])

Since a job id can be traced to its parent workflow, the above change would allow the parent workflow to be traced back to its parent workflow, and so on...