[RFE] Additional information required in logs for tasks

[chargio]

When creating logs for tasks, ManageIQ stores the task ID. When the task is part of a service, correlation of service to task is difficult, as implies looking for information in the log file when the task is created.
Service information should be added to tasks when they are related to a service.

[chargio]

We propose to do this adding two columns to the miq table to create a polymorphic association to the parent element:

• A parent_id
• A parent_type
  So any task is associated to the reponsible for creating it (request, service, other task, etc).
  In that way, logs could be enhanced with this information and thus you should be able to follow that relationship in log management tools like Splunk, Logstash, etc.

[chargio]

@pemcg Please review

[pemcg]

I also submitted an RFE on this: https://bugzilla.redhat.com/show_bug.cgi?id=1386108, although this only mentions adding the request ID. Sergio's suggestion of adding a generic parent id would definitely improve on this.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

[gmcculloug]

A logging change was introduced in #17013 (March 2018) which adds the request id into the log prefix to make it easier to identify request and task relationships.

This solution was used to close the BZ referenced above: https://bugzilla.redhat.com/show_bug.cgi?id=1386108