chore: regenerate stale .pi-map.md / .pi-map.index.md project maps
Project map had drifted: claimed recharts unused (was used), ObservabilityPage.tsx
exists (refactored to service-tabs/), missed JellyfinNowPlayingWidget +
authentik/backups service types. Regenerate to reflect post-change reality:
new Qbittorrent/LineSeriesChart/Prometheus{Gauge,Mean}Widget files,
service_data.py/qbittorrent_store.py, canonical prometheus-charting +
service-storage specs, archived changes.
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
dir: monitoring/alertmanager
|
||||
|
||||
## role
|
||||
Central configuration package for Prometheus alert routing, grouping, and notification delivery within the monitoring stack.
|
||||
Manages alert routing, grouping, and notification delivery for Prometheus-generated alerts via email and webhook channels.
|
||||
## parent
|
||||
index: monitoring/.pi-map.index.md
|
||||
map: monitoring/.pi-map.md
|
||||
|
||||
@@ -4,11 +4,11 @@ dir: monitoring/alertmanager
|
||||
index: monitoring/alertmanager/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Central configuration package for Prometheus alert routing, grouping, and notification delivery within the monitoring stack.
|
||||
Manages alert routing, grouping, and notification delivery for Prometheus-generated alerts via email and webhook channels.
|
||||
## files
|
||||
- alertmanager.yml | Configures Alertmanager for routing, grouping, and delivering Prometheus alerts via email and webhook with support for critical alert escalation and inhibition rules. | dep: Alertmanager, SMTP server, webhook endpoint, environment variables (SMTP_HOST, SMTP_PORT, SMTP_FROM_ADDRESS, SMTP_USERNAME, SMTP_PASSWORD, ALERT_EMAIL_TO, ALERTMANAGER_WEBHOOK_URL)
|
||||
## arch
|
||||
Declarative YAML configuration utilizing a hierarchical routing tree with receiver-based notification patterns (email, webhook) and alert inhibition rules to prevent notification storms.
|
||||
Declarative YAML configuration implementing rule-based routing, alert grouping, inhibition policies, and critical escalation patterns.
|
||||
## tags
|
||||
alertmanager, configures, routing, grouping, delivering, prometheus, alerts, email
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user