chore(deps): update helm release generic-prometheus-alerts to v1.11.3

[renovate]

This PR contains the following updates:

Package	Update	Change
generic-prometheus-alerts	minor	1.3.2 -> 1.11.3

---

Release Notes

ministryofjustice/hmpps-helm-charts (generic-prometheus-alerts)

v1.11.3

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.11.2

Compare Source

Various fixes to the elasticache alert yaml

v1.11.1

Compare Source

Fixes to the default elasticache alert thresholds.

v1.11.0

Compare Source

Update to Elasticache alerts, separating out the following alerts:

• elasticache-freeable-memory (alert on a minimum FreeableMemory threshold)
• elasticache-memory-utilisation (alert on a maximum DatabaseMemoryUsagePercentage threshold)

To configure Elasticache alerts, add into the helm values file under generic-prometheus-alerts: a list of cluster ids to monitor. For example:

elastiCacheAlertsClusterIds:
  elasticache-cluster-id: "Meaningful cluster display name"
  elasticache-cluster-2-id: "Meaningful cluster display name 2"

The alert thresholds can be configured with the following parameters:

### Maxiumum threshold for Elasticache EngineCPUUtilisation - value between 0 and 100.
elastiCacheAlertsEngineCPUThreshold: 85
### Duration over which to measure Elasticache EngineCPUUtilisation (minutes).
elastiCacheAlertsEngineCPUThresholdMinutes: 5
### Maximum threshold for Elasticache CPUUtilisation - value between 0 and 100.
elastiCacheAlertsCPUThreshold: 90
### Duration over which to measure Elasticache CPUUtilisation (minutes).
elastiCacheAlertsCPUThresholdMinutes: 5
### Minimum threshold for Elasticache FreeMemory - value should be above 150MB.
elastiCacheAlertsFreeMemoryThreshold: 150
### Duration over which to measure Elasticache FreeMemory (minutes).
elastiCacheAlertsFreeMemoryThresholdMinutes: 5
### Maximum threshold for Elasticache DatabaseMemoryUsagePercentage - value between 0 and 100.
elastiCacheAlertsMemoryUsageThreshold: 75
### Duration over which to measure Elasticache DatabaseMemoryUsagePercentage (minutes).
elastiCacheAlertsMemoryUsageThresholdMinutes: 5

v1.10.0

Compare Source

Add in ingress 2xx response monitoring (default disabled) to ensure that enough traffic is going to a service.

Can be enabled by setting ingress2xxEnabled to true.
Controlled by:

• ingress2xxWindowMinutes: number of minutes to sample over, default 60.
• ingress2xxThreshold: number of requests to expect in the time window, default 100.

v1.9.0

Compare Source

Remove old unused applicationAlertsEnabled configuration. See #​157 for changes.

v1.8.0

Compare Source

Add in sqsNumberAlertQueueMappings new functionality to create separate prometheus alerts per mapping rather than one alert for all the queues. This then means that separate alerts are created in slack for each one and aren't included in a Show more group.

v1.7.0

Compare Source

https://github.com/ministryofjustice/hmpps-helm-charts/pull/152: Attempt to stop failing cronjobs from falsely being marked as resolved if they are actually running at the time that they are checked by Prometheus. We do this by counting the failures over the last 5 minutes (configurable by applicationCronJobStatusFailedWindowMinutes) rather than at a specific point in time.

v1.6.0

Compare Source

Increases the threshold for the 5xxErrorResponsesOnHealthEndpoint alert from 0 to 0.004 (configurable via the ingress5xxHealthEndpointThreshold property`). This is to attempt to stop false positives from firing for health alerts.

v1.5.0

Compare Source

Remove KubeCronJobRunning job as was causing lots of false positives

v1.4.1

Compare Source

Bug fix release so that when applicationAlertsEnabled is set to false no alert rules are created.

v1.4.0

Compare Source

Add in ability to turn off the application alerts by setting applicationAlertsEnabled to false

v1.3.12

Compare Source

5xxErrorResponses alert altered to now target all paths except /health (bug introduced in 1.3.9 that meant that it only targetted /).

v1.3.11

Compare Source

Do not use - broken since 1.3.9. Fixed in 1.3.12. Updated alert test rule path

v1.3.10

Compare Source

Do not use - broken since 1.3.9. Fixed in 1.3.12. Creates a set of standard prometheus alert rules for a given application

v1.3.9

Compare Source

Do not use - ingress matching and path matching broken in this version. Fixed in 1.3.12.

v1.3.8

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.3.7

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.3.6

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.3.5

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.3.4

Compare Source

Creates a set of standard prometheus alert rules for a given application

v1.3.3

Compare Source

Creates a set of standard prometheus alert rules for a given application

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.