Skip to content

Unify AlertManager alert naming #451

@jb3

Description

@jb3

Whilst we use the same alerting policies for both Kubernetes and Netcup, we haven't yet unified the naming.

Kubernetes is styled as ContainerOOMEvents whilst Netcup has something like node/systemd-unit-failed.

We should rename the Kubernetes alerts to use the latters styling. We can prefix the alerts with the group they are in (e.g. coredns, cert-manager) followed by the previous alert name but as a slug (e.g. KubernetesPodCrashLooping to kubernetes/pod-crash-looping)

Metadata

Metadata

Assignees

Labels

component: monitoringAn issue relating to a monitoring component (e.g. Prometheus, Grafana)group: kubernetesIssues and pull requests related to the Kubernetes setupwebscale

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions