Chapter 2. Monitoring

Procedure

1. In the Developer perspective of the web console, select the namespace where your Argo CD application is installed, and navigate to Observe Metrics.
2. From the Select query drop-down list, select Custom query.

3. To check the health status of your Argo CD application, enter the Prometheus Query Language (PromQL) query similar to the following example in the Expression field:

   Example

   sum(argocd_app_info{dest_namespace=~"<your_defined_namespace>",health_status!=""}) by (health_status) 

   1

   Copy to Clipboard Toggle word wrap

   1

   Replace the <your_defined_namespace> variable with the actual name of your defined namespace, for example openshift-gitops.

Procedure

1. Click Environments under the Developer perspective. The Environments page shows the list of applications along with their Environment status.
2. Hover over the icons under the Environment status column to see the synchronization status of all the environments.
3. Click the application name from the list to view the details of a specific application.

4. In the Application environments page, if the Resources section under the Overview tab displays icons, hover over the icons to get status details.

   • A broken heart indicates that resource issues have degraded the application’s performance.
   • A yellow yield sign indicates that resource issues have delayed data about the application’s health.
5. To view the deployment history of an application, click the Deployment History tab. The page includes details such as the Last deployment, Description (commit message), Environment, Author, and Revision.

Procedure

1. Set the .spec.monitoring.enabled field value to true on a given Argo CD instance:

   Example Argo CD custom resource

   apiVersion: argoproj.io/v1alpha1
   kind: ArgoCD
   metadata:
     name: example-argocd
     labels:
       example: repo
   spec:
     ...
     monitoring:
       enabled: true
     ...

   Copy to Clipboard Toggle word wrap

2. Verify whether an alert rule is included in the PrometheusRule created by the Operator:

   Example alert rule

   apiVersion: monitoring.coreos.com/v1
   kind: PrometheusRule
   metadata:
     name: argocd-component-status-alert
     namespace: openshift-gitops
   spec:
     groups:
       - name: ArgoCDComponentStatus
         rules:
           ...
           - alert: ApplicationSetControllerNotReady 

   1

   
             annotations:
               message: >-
                 applicationSet controller deployment for Argo CD instance in
                 namespace "default" is not running
             expr: >-
               kube_statefulset_status_replicas{statefulset="openshift-gitops-application-controller statefulset",
               namespace="openshift-gitops"} !=
               kube_statefulset_status_replicas_ready{statefulset="openshift-gitops-application-controller statefulset",
               namespace="openshift-gitops"}
             for: 1m
             labels:
               severity: critical

   Copy to Clipboard Toggle word wrap

   1

   Alert rule in the PrometheusRule that checks whether the workloads created by the Argo CD instances are running as expected.