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:
Developer
2026-07-09 14:05:56 +00:00
parent 98f17f6e5d
commit ec7ebd7013
189 changed files with 1215 additions and 428 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
dir: monitoring/alloy
## role
Centralized log collection configuration that scrapes Docker container logs and forwards them to Loki for storage and querying.
Centralized configuration for collecting and forwarding container logs to the monitoring system's log aggregation backend.
## parent
index: monitoring/.pi-map.index.md
map: monitoring/.pi-map.md
+2 -2
View File
@@ -4,11 +4,11 @@ dir: monitoring/alloy
index: monitoring/alloy/.pi-map.index.md
## role
Centralized log collection configuration that scrapes Docker container logs and forwards them to Loki for storage and querying.
Centralized configuration for collecting and forwarding container logs to the monitoring system's log aggregation backend.
## files
- config.alloy | Configures Alloy to scrape Docker container logs and forward them to a local Loki instance | dep: docker, loki, discovery.docker, discovery.relabel, loki.source.docker, loki.write
## arch
Declarative agent-based collection pattern using Grafana Alloy's discovery and pipeline stages to discover containers, tail their logs, and stream them to a local Loki destination.
Declarative agent-based collection pattern using Grafana Alloy's pipeline architecture to scrape Docker logs and ship them to Loki.
## tags
docker, loki, discovery, config, configures, alloy, scrape, container
## symbols