You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hugo/content/en/monitoring/_index.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,14 @@ These Stack is based on:
13
13
14
14
CPO has prepared an own Exporter for the PostgreSQl-Pod which can used as a sidecar.
15
15
16
+
#### Configure Cluster for monitoring
17
+
To deploy a monitoring exporter for Prometheus and create the necessary users and permissions in the cluster, the cluster manifest must be extended to include the `monitor` object.
18
+
-`customQueries`: Name of the ConfigMap containing custom queries for PostgreSQL and Prometheus.
19
+
-`env`: Additional environment variables for the sidecar container
20
+
-`image`: Image for the monitoring sidecar. For example: `containers.cybertec.at/cybertec-pg-container/exporter:rocky9-18.3-2`
21
+
22
+
{{< hint type=Info >}}The ConfigMap is mounted in the sidecar container. Any additional permissions required for the queries must be manually granted to the monitoring user if necessary.{{< /hint >}}
23
+
16
24
#### Setting up the Monitoring Stack
17
25
To setup the Monitoring-Stack we suggest that you create an own namespace and use the prepared kustomization file inside the Operator-Tutorials.
18
26
```
@@ -24,7 +32,7 @@ No resources found in cpo-monitoring namespace.
# Hint: Please check if youn want to use a specific storage-class the file pvcs.yaml and add your storageclass on the commented part. Please ensure that you removed the comment-char.
35
+
{{< hint type=Info >}}Hint: Please check if you want to use a specific storage-class the file pvcs.yaml and add your storageclass on the commented part. Please ensure that you removed the comment-char.{{< /hint >}}
28
36
29
37
$ kubectl apply -n cpo-monitoring -k .
30
38
serviceaccount/cpo-monitoring created
@@ -47,9 +55,9 @@ deployment.apps/cpo-monitoring-alertmanager created
47
55
deployment.apps/cpo-monitoring-grafana created
48
56
deployment.apps/cpo-monitoring-prometheus created
49
57
50
-
Hint: If you're not running Openshift you will get a error like this:
58
+
{{< hint type=Info >}}Hint: If you're not running Openshift you will get a error like this:
51
59
error: resource mapping not found for name: "grafana" namespace: "" from ".":
52
-
no matches for kind "Route" in version "route.openshift.io/v1" ensure CRDs are installed first
60
+
no matches for kind "Route" in version "route.openshift.io/v1" ensure CRDs are installed first{{< /hint >}}
53
61
54
62
You can ignore this, because it depends on an object with the type route which is part of Openshift.
55
63
It is not needed replaced by ingress-rules or an loadbalancer-service.
0 commit comments