-
-
Notifications
You must be signed in to change notification settings - Fork 6
Unify AlertManager alert naming #451
Copy link
Copy link
Closed
Labels
component: monitoringAn issue relating to a monitoring component (e.g. Prometheus, Grafana)An issue relating to a monitoring component (e.g. Prometheus, Grafana)group: kubernetesIssues and pull requests related to the Kubernetes setupIssues and pull requests related to the Kubernetes setupwebscale
Metadata
Metadata
Assignees
Labels
component: monitoringAn issue relating to a monitoring component (e.g. Prometheus, Grafana)An issue relating to a monitoring component (e.g. Prometheus, Grafana)group: kubernetesIssues and pull requests related to the Kubernetes setupIssues and pull requests related to the Kubernetes setupwebscale
Type
Projects
Status
Done
Whilst we use the same alerting policies for both Kubernetes and Netcup, we haven't yet unified the naming.
Kubernetes is styled as
ContainerOOMEventswhilst Netcup has something likenode/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.KubernetesPodCrashLoopingtokubernetes/pod-crash-looping)