mirror of
https://github.com/ryan4yin/nix-config.git
synced 2026-11-13 12:13:36 +01:00
Ryan Yin
c292509351
Aquamarine's services now run directly on kubevirt-youko, so the guest definition is no longer needed: - move its service modules to hosts/k8s/kubevirt-youko/aquamarine/ and drop the explicit import list, leaving aquamarine-services.nix with just its IP and secret groups - delete the guest base, journald override, output entry and home config - repoint the eval tests that read the guest's config to kubevirt-youko - drop the now-dead 'aqua' colmena recipe and its image upload The aqua KubeVirt VM itself is deleted separately; the name is kept in the docs for a possible later test microvm/qemu-vm on idols-ai.
58 lines
2.3 KiB
YAML
58 lines
2.3 KiB
YAML
groups:
|
|
- name: general.rules
|
|
rules:
|
|
- alert: TargetDown
|
|
annotations:
|
|
description:
|
|
'{{ printf "%.4g" $value }}% of the {{ $labels.job }}/{{ $labels.service }} targets in
|
|
{{ $labels.namespace }} namespace are down.'
|
|
runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/targetdown
|
|
summary: One or more targets are unreachable.
|
|
expr:
|
|
100 * (count(up == 0) BY (cluster, job, namespace, service) / count(up) BY (cluster, job,
|
|
namespace, service)) > 10
|
|
for: 10m
|
|
labels:
|
|
severity: warning
|
|
- alert: Watchdog
|
|
annotations:
|
|
description: 'This is an alert meant to ensure that the entire alerting pipeline is
|
|
functional.
|
|
|
|
This alert is always firing, therefore it should always be firing in Alertmanager
|
|
|
|
and always fire against a receiver. There are integrations with various notification
|
|
|
|
mechanisms that send a notification when this alert is not firing. For example the
|
|
|
|
"DeadMansSnitch" integration in PagerDuty.'
|
|
runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/watchdog
|
|
summary:
|
|
An alert that should always be firing to certify that Alertmanager is working properly.
|
|
expr: vector(1)
|
|
labels:
|
|
severity: none
|
|
- alert: InfoInhibitor
|
|
annotations:
|
|
description: 'This is an alert that is used to inhibit info alerts.
|
|
|
|
By themselves, the info-level alerts are sometimes very noisy, but they are relevant
|
|
when combined with
|
|
|
|
other alerts.
|
|
|
|
This alert fires whenever there''s a severity="info" alert, and stops firing when
|
|
another alert with a
|
|
|
|
severity of ''warning'' or ''critical'' starts firing on the same namespace.
|
|
|
|
This alert should be routed to a null receiver and configured to inhibit alerts with
|
|
severity="info".'
|
|
runbook_url: https://runbooks.prometheus-operator.dev/runbooks/general/infoinhibitor
|
|
summary: Info-level alert inhibition.
|
|
expr:
|
|
ALERTS{severity = "info"} == 1 unless on(namespace) ALERTS{alertname != "InfoInhibitor",
|
|
severity =~ "warning|critical", alertstate="firing"} == 1
|
|
labels:
|
|
severity: none
|