Business Problem:

[Explain the business problem that the customer is trying to solve. There may be several ways to address it, so the more context you provide, the better solution we can design]

 The customer in case 03770452 is requesting that RHACS retain process activity for inactive pods for a limited time to assist with investigations.   Per our documentation, 

Red Hat Advanced Cluster Security for Kubernetes shows events only for the active pods.

The customer proposes that RHACS allow a limited retention time to process activity logs for inactive pods, allowing customers to download this information in a CSV report to continue an investigation.   Per the customer:

 My suggestion is to add an option to save the process activity of inactive pods for some time. When investigating a pod, if it is already deleted, there is no access to its "process activity" and deployment "risk", which makes the investigation a lot harder. Adding retention time to this will allow to download the process activity as CSV and continue the investigation.

Use Cases:

[Describe specific scenarios or situations where the feature would be useful]

When investigating issues, the lack of visibility into the process activity of the deleted pod makes it more difficult. 

Key Functionality:

[Outline the main functions and capabilities of the feature]

• Retain process activity logs for deleted pods for a limited amount of time. 
• Ability to download a CSV report with this activity

Benefits:

[Highlight the benefits/advantages of the suggested feature if not addressed above]]

Acceptance criteria:

[Describe the key features that need to be covered by the feature to be able to satisfy the customer]

Implementation Suggestions (optional):

• Integration: [Specify any existing systems or tools that the new feature should integrate with]

• Dependencies: [Describe any dependencies on other 3rd party integrations or OCP components] 

• User Experience: [Provide suggestions for designing the UI to optimize usability. Highlight other relevant aspects of the user experience ]

Timeline:

[Specify the preferred implementation date or any specific deadlines for the feature implementation]

Please use the following Jira fields to complete this Feature Request

1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
2. [Jira Field] Description:
3. [Jira Field] Component:
4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]

1. [Jira Field] Supporting Documentation:
    

1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]