Operator
Infrastructure
Stabilize the payments-api workload by investigating the OOM/restart loop: review container logs, confirm the crash reason, and either raise memory headroom or reduce memory consumption before reintroducing traffic.
Harden the container spec: run as a non-root UID, disable privilege escalation, remove any unnecessary capability, and convert the root filesystem and config mount to read-only where feasible.
Reduce exposure of sensitive mounted data by minimizing host-path mounts and tightly controlling the mounted payments secret; rotate the secret if there is any chance the container was compromised during the restart loop.
Runtime state, restart history, and memory safety signals from the submitted container diagnostics artifact.
Resource and hardening context that shapes how the runtime snapshot should be interpreted.
Compact one-shot CPU and memory bars so the operator can judge runtime pressure without reading raw numbers.
A compact operator view of severity and signal distribution before you drop into detailed findings.
Filter the findings table by signal or severity while keeping the current visible count in view.
Detailed review
Expanded explanation for operators who want the model summary after reviewing the findings table.