mirrors/oneuptime
1
0
Fork 0
mirror of https://github.com/OneUptime/oneuptime synced 2024-11-21 22:59:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: Update OneUptime chart to use probes instead of probe for probe configuration

Browse Source 
This commit modifies the OneUptime chart to use the `probes` parameter instead of the `probe` parameter for configuring probes. The `probes` parameter now accepts a key-value pair where the key represents the probe name and the value contains the probe configuration details. This change improves the clarity and consistency of the chart configuration, making it easier to manage and maintain.

Files modified:
- HelmChart/Public/oneuptime/README.md
This commit is contained in:
Simon Larsen 2024-08-01 08:22:51 -06:00
parent 88216cdebb
commit 2c5bbbb6da
No known key found for this signature in database
GPG Key ID: 96C5DCA24769DBCA
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
HelmChart/Public/oneuptime/README.md
View File

@ -92,13 +92,13 @@ The following table lists the configurable parameters of the OneUptime chart and
| `nginx.service.type` | nginx service type | `LoadBalancer` | |
| `nginx.service.loadBalancerIP` | nginx service load balancer IP | `nil` | |
| `deployment.replicaCount` | Number of replicas | `1` | |
| `probe.<key>.name` | Probe name | `<key>` | |
| `probe.<key>.description` | Probe description | `nil` | |
| `probe.<key>.key` | Probe key. Please set this to long random string to secure your probes. | `nil` | |
| `probe.<key>.monitoringWorkers` | Number of threads / parallel processes you need to monitor your resources | `3` | |
| `probe.<key>.monitorFetchLimit` | Number of resources to be monitored in parallel | `10` | |
| `probe.<key>.syntheticMonitorScriptTimeoutInMs` | Timeout for synthetic monitor script | `60000` | |
| `probe.<key>.customCodeMonitorScriptTimeoutInMs` | Timeout for custom code monitor script | `60000` | |
| `probes.<key>.name` | Probe name | `<key>` | |
| `probes.<key>.description` | Probe description | `nil` | |
| `probes.<key>.key` | Probe key. Please set this to long random string to secure your probes. | `nil` | |
| `probes.<key>.monitoringWorkers` | Number of threads / parallel processes you need to monitor your resources | `3` | |
| `probes.<key>.monitorFetchLimit` | Number of resources to be monitored in parallel | `10` | |
| `probes.<key>.syntheticMonitorScriptTimeoutInMs` | Timeout for synthetic monitor script | `60000` | |
| `probes.<key>.customCodeMonitorScriptTimeoutInMs` | Timeout for custom code monitor script | `60000` | |
| `statusPage.cnameRecord` | CNAME record for the status page | `nil` | |
| `internalSmtp.sendingDomain` | Domain to send emails from | `nil` | |
| `internalSmtp.dkimPrivateKey` | DKIM Private Key that is set for sending domain | `nil` | |
@ -308,7 +308,7 @@ Please do the same for Redis and Clickhouse.
- [ ] Please make sure you have a backups enabled for your PVCs. This is outside the scope of this chart. Please refer to your cloud provider's documentation on how to enable backups for PVCs.
- [ ] Please make sure you have static passwords for your database passswords (for redis, clickhouse and postgres). You can refer to Bitnami documentation on how to set static passwords for these databases.
- [ ] Please set `oneuptimeSecret` and `encryptionSecret` to a long random string. You can use a password generator to generate these strings.
- [ ] Please set `probe.<key>.key` to a long random string. This is used to secure your probes.
- [ ] Please set `probes.<key>.key` to a long random string. This is used to secure your probes.
- [ ] Please regularly update OneUptime. We release updates every day. We recommend you to update the software aleast once a week if you're running OneUptime production.
## Releases