*Description: *

Currently, our AAP deployments on RHEL installations lack sufficient visibility into resource consumption. I propose the implementation of a minimal, yet critical, feature that will provide users and administrators with valuable insights into CPU, disk, images and memory usage.

Rationale:

In our current setup, determining CPU and memory consumption in advance is challenging due to the dynamic nature of the rulebook content and the flow of incoming events.

While k8s/ocp installations enjoy scalability and integrated resource monitoring tools, the situation is more critical for deployments using podman. Unlike k8s/ocp, podman's scalability is limited to vertical scaling, making it vulnerable to unexpected behavior when VMs host an excessive number of activations, if some activations have intense resource consumption. Also the our reliance on local hard disks presents a challenge, as multiple DD's images can exhaust disk space.

Expected Benefits:

The proposed feature enhancement offers several benefits:

• Empower users and administrators with visibility into resource consumption.
• Facilitate proactive management of activations to prevent unpredictable behavior.

I believe that the implementation of enhanced resource consumption visibility will significantly improve the reliability, predictability, and overall experience of our AAP deployments on RHEL installations. This feature aligns our offerings more closely with the scalability and resource management benefits of k8s/ocp deployments.