ML-RHDEVDOCS-2756: Added a new section for monitoring Argo CD instances

_topic_maps/_topic_map.yml

@@ -232,8 +232,6 @@ Topics:
     File: installing-azure-stack-hub-network-customizations
   - Name: Installing a cluster on Azure Stack Hub using ARM templates
     File: installing-azure-stack-hub-user-infra
-  - Name: Installation configuration parameters for Azure Stack Hub
-    File: installation-config-parameters-ash
   - Name: Uninstalling a cluster on Azure Stack Hub
     File: uninstalling-cluster-azure-stack-hub
 - Name: Installing on GCP
@@ -322,8 +320,6 @@ Topics:
     File: installing-restricted-networks-bare-metal
   - Name: Scaling a user-provisioned installation with the bare metal operator
     File: scaling-a-user-provisioned-cluster-with-the-bare-metal-operator
-  - Name: Installation configuration parameters for bare metal
-    File: installation-config-parameters-bare-metal
 - Name: Installing on-premise with Assisted Installer
   Dir: installing_on_prem_assisted
   Distros: openshift-enterprise
@@ -525,19 +521,8 @@ Topics:
 - Name: Bare metal configuration
   File: bare-metal-configuration
 - Name: Configuring multi-architecture compute machines on an OpenShift cluster
-  Dir: configuring-multi-arch-compute-machines
   Distros: openshift-enterprise
-  Topics:
-  - Name: About clusters with multi-architecture compute machines
-    File: multi-architecture-configuration
-  - Name: Creating a cluster with multi-architecture compute machines on Azure
-    File: creating-multi-arch-compute-nodes-azure
-  - Name: Creating a cluster with multi-architecture compute machines on AWS
-    File: creating-multi-arch-compute-nodes-aws
-  - Name: Creating a cluster with multi-architecture compute machines on bare metal
-    File: creating-multi-arch-compute-nodes-bare-metal
-  - Name: Managing your cluster with multi-architecture compute machines
-    File: multi-architecture-compute-managing
+  File: multi-architecture-configuration
 - Name: Enabling encryption on a vSphere cluster
   File: vsphere-post-installation-encryption
 - Name: Machine configuration tasks
@@ -1547,8 +1532,6 @@ Topics:
       File: persistent-storage-hostpath
     - Name: Persistent storage using LVM Storage
       File: persistent-storage-using-lvms
-    - Name: Troubleshooting local persistent storage using LVMS
-      File: troubleshooting-local-persistent-storage-using-lvms
 - Name: Using Container Storage Interface (CSI)
   Dir: container_storage_interface
   Distros: openshift-enterprise,openshift-origin
@@ -1944,8 +1927,8 @@ Topics:
     File: uninstalling-openshift-gitops
   - Name: Setting up a new Argo CD instance
     File: setting-up-argocd-instance
-  - Name: Using Argo Rollouts for progressive deployment delivery
-    File: using-argo-rollouts-for-progressive-deployment-delivery
+  - Name: Monitoring Argo CD instances
+    File: monitoring-argo-cd-instances
   - Name: Configuring an OpenShift cluster by deploying an application with cluster configurations
     File: configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations
   - Name: Deploying a Spring Boot application with Argo CD
@@ -3644,23 +3627,18 @@ Topics:
   - Name: Installing OKD Virtualization
     File: installing-virt
     Distros: openshift-origin
+  - Name: Specifying nodes for OpenShift Virtualization components
+    File: virt-specifying-nodes-for-virtualization-components
+    Distros: openshift-enterprise
+  - Name: Specifying nodes for OKD Virtualization components
+    File: virt-specifying-nodes-for-virtualization-components
+    Distros: openshift-origin
   - Name: Uninstalling OpenShift Virtualization
     File: uninstalling-virt
     Distros: openshift-enterprise
   - Name: Uninstalling OKD Virtualization
     File: uninstalling-virt
     Distros: openshift-origin
-- Name: Post-installation configuration
-  Dir: post_installation_configuration
-  Topics:
-  - Name: Post-installation configuration
-    File: virt-post-install-config
-  - Name: Node placement rules
-    File: virt-node-placement-virt-components
-  - Name: Network configuration
-    File: virt-post-install-network-config
-  - Name: Storage configuration
-    File: virt-post-install-storage-config
 - Name: Updating
   Dir: updating
   Topics:
@@ -3702,10 +3680,6 @@ Topics:
     File: virt-using-vtpm-devices
   - Name: Managing virtual machines with OpenShift Pipelines
     File: virt-managing-vms-openshift-pipelines
-  - Name: Managing automatic boot source updates
-    File: virt-automatic-bootsource-updates
-  - Name: Creating custom boot sources
-    File: virt-creating-and-using-boot-sources
   - Name: Advanced virtual machine management
     Dir: advanced_vm_management
     Topics:
@@ -3759,7 +3733,7 @@ Topics:
     - Name: Cloning a virtual machine by using a data volume template
       File: virt-cloning-vm-using-datavolumetemplate
     - Name: Cloning a virtual machine disk into a new block storage persistent volume claim
-      File: virt-cloning-vm-disk-to-new-block-storage-pvc
+      File: virt-cloning-vm-disk-into-new-block-storage-pvc
 #A BETTER NAME THAN 'STORAGE 4 U'
   - Name: Virtual machine disks
     Dir: virtual_disks
@@ -3825,6 +3799,25 @@ Topics:
     File: virt-accessing-vm-secondary-network-fqdn
   - Name: Managing MAC address pools for network interfaces
     File: virt-using-mac-address-pool-for-vms
+# Templates
+- Name: Virtual machine templates
+  Dir: vm_templates
+  Topics:
+  - Name: Creating virtual machine templates
+    File: virt-creating-vm-template
+  - Name: Editing virtual machine templates
+    File: virt-editing-vm-template
+  - Name: Enabling dedicated resources for a virtual machine template
+    File: virt-dedicated-resources-vm-template
+  - Name: Deploying a virtual machine template to a custom namespace
+    File: virt-deploying-vm-template-to-custom-namespace
+  - Name: Deleting a virtual machine template
+    File: virt-deleting-vm-template
+  - Name: Creating and using boot sources
+    File: virt-creating-and-using-boot-sources
+  - Name: Managing automatic boot source updates
+    File: virt-automatic-bootsource-updates
+    Distros: openshift-enterprise
 # Virtual machine live migration
 - Name: Live migration
   Dir: live_migration

cicd/gitops/monitoring-argo-cd-instances.adoc

@@ -0,0 +1,17 @@
+:_content-type: ASSEMBLY
+[id="monitoring-argo-cd-instances"]
+= Monitoring Argo CD instances
+include::_attributes/common-attributes.adoc[]
+:context: monitoring-argo-cd-instances
+
+toc::[]
+
+By default, the {gitops-title} Operator automatically detects an installed Argo CD instance in your defined namespace, for example, `openshift-gitops`, and connects it to the monitoring stack of the cluster to provide alerts for out-of-sync applications.
+
+.Prerequisites
+* You have access to the cluster with `cluster-admin` privileges.
+* You have access to the {product-title} web console.
+* You have installed the {gitops-title} Operator in your cluster.
+* You have installed an Argo CD application in your defined namespace, for example, `openshift-gitops`.
+
+include::modules/gitops-monitoring-argo-cd-health-using-prometheus-metrics.adoc[leveloffset=+1]

modules/gitops-monitoring-argo-cd-health-using-prometheus-metrics.adoc

@@ -0,0 +1,24 @@
+// Module included in the following assemblies:
+//
+// * cicd/gitops/monitoring-argo-cd-instances.adoc
+
+:_content-type: PROCEDURE
+[id="gitops-monitoring-argo-cd-health-using-promethous-metrics_{context}"]
+= Monitoring Argo CD health using Prometheus metrics
+
+You can monitor the health status of an Argo CD application by running Prometheus metrics queries against it.
+
+.Procedure
+
+. In the *Developer* perspective of the web console, select the namespace where your Argo CD application is installed, and navigate to *Observe* -> *Metrics*.
+. From the *Select query* drop-down list, select *Custom query*.
+. 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
+[source, query]
+----
+sum(argocd_app_info{dest_namespace=~"<your_defined_namespace>",health_status!=""}) by (health_status) <1>
+----
+<1> Replace the `<your_defined_namespace>` variable with the actual name of your defined namespace, for example `openshift-gitops`.
+
+