Degraded health status in Application Controller

Resource Reconciliation Failure

In Argo CD, the Application Controller monitors the desired state in Git against the actual state in the Kubernetes cluster. When a synchronization operation fails, the application health status often transitions to Degraded.

This status is a generic indicator that can be triggered by various underlying issues, such as failed sync hooks or API server communication errors. While the argocd-application-controller pod logs provide traces for reconciliation loops, identifying the specific resource causing the degradation requires correlating controller logs with individual resource events.

Given the generic nature of the health status, what is the most efficient method to isolate the specific failing resource within the controller logs? How can log verbosity be tuned to capture detailed reconciliation events without impacting controller performance?