-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ml-jira-2756:Documented monitoring Argo CD instances
- Loading branch information
1 parent
cefd8fe
commit 561ef91
Showing
3 changed files
with
43 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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] |
24 changes: 24 additions & 0 deletions
24
modules/gitops-monitoring-argo-cd-health-using-prometheus-metrics.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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`. | ||
|
||
|