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: README.md
+20-9Lines changed: 20 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ A reference for tools, configurations, and documentation used to monitor CircleC
5
5
6
6
This repository is currently under active development and is not yet a supported resource. Please refer to it at your own discretion until further notice.
7
7
8
-
# circleci-server-monitoring-stack
8
+
# server-monitoring-stack
9
9
10
10
A reference Helm chart for setting up a monitoring stack for CircleCI server
11
11
@@ -34,25 +34,32 @@ telegraf:
34
34
listen: ":9273"
35
35
```
36
36
37
-
### 2. Install Dependencies
37
+
### 3. Add Helm Repository
38
+
39
+
First, add the CircleCI Server Monitoring Stack Helm repository:
Before installing the full chart, you must first install the dependency subcharts, including the Prometheus Custom Resource Definitions (CRDs) and the Grafana operator chart. This assumes you are installing it in the same namespace as your CircleCI server installation:
> **_NOTE:_** It's possible to install the monitoring stack in a different namespace than the CircleCI server installation. If you do so, set the `prometheus.serviceMonitor.selectorNamespaces` value with the target namespace.
46
53
47
-
### 3. Install the Helm Chart
54
+
### 4. Install the Helm Chart
48
55
49
56
Next, install the Helm chart using the following command:
| prometheusOperator.prometheusConfigReloader.image.tag | string | `"v0.80.1"` | Tag for the Prometheus Config Reloader image. |
168
175
| prometheusOperator.replicas | int | `1` | Number of Prometheus Operator replicas to deploy. |
176
+
177
+
## Releasing
178
+
179
+
Releases are managed by the CI/CD pipeline on the main branch, with an approval job gate called `approve-deploy-chart`. Before releasing, increment the Helm chart version in `Chart.yaml` and regenerate the documentation using `./do helm-docs`. Once approved, the release will be available in the [package repository](https://packagecloud.io/circleci/server-monitoring-stack).
Before installing the full chart, you must first install the dependency subcharts, including the Prometheus Custom Resource Definitions (CRDs) and the Grafana operator chart. This assumes you are installing it in the same namespace as your CircleCI server installation:
> **_NOTE:_** It's possible to install the monitoring stack in a different namespace than the CircleCI server installation. If you do so, set the `prometheus.serviceMonitor.selectorNamespaces` value with the target namespace.
40
47
41
-
### 3. Install the Helm Chart
48
+
### 4. Install the Helm Chart
42
49
43
50
Next, install the Helm chart using the following command:
### 4. Verify Prometheus Is Up and Targeting Telegraf
56
+
### 5. Verify Prometheus Is Up and Targeting Telegraf
50
57
To verify that Prometheus is working correctly and targeting Telegraf, use the following command to port-forward Prometheus:
51
58
52
59
```bash
@@ -57,7 +64,7 @@ Then visit http://localhost:9090/targets in your browser. Verify that Telegraf a
57
64
58
65

59
66
60
-
### 5. Verify Grafana Is Up and Connected to Prometheus
67
+
### 6. Verify Grafana Is Up and Connected to Prometheus
61
68
62
69
To verify that Grafana is working correctly and connected to Prometheus, use the following command to port-forward Grafana:
63
70
```bash
@@ -68,7 +75,7 @@ Then visit http://localhost:3000 in your browser. Once logged in with the defaul
68
75
69
76

70
77
71
-
### 6. Next Steps
78
+
### 7. Next Steps
72
79
73
80
After ensuring both Prometheus and Grafana are operational, consider these enhancements:
74
81
@@ -108,3 +115,7 @@ grafana:
108
115
> **_NOTE:_** Use a custom storage class with a 'Retain' policy to secure data integrity.
109
116
110
117
{{ template "chart.valuesSection" . }}
118
+
119
+
## Releasing
120
+
121
+
Releases are managed by the CI/CD pipeline on the main branch, with an approval job gate called `approve-deploy-chart`. Before releasing, increment the Helm chart version in `Chart.yaml` and regenerate the documentation using `./do helm-docs`. Once approved, the release will be available in the [package repository](https://packagecloud.io/circleci/server-monitoring-stack).
0 commit comments