9b154d38f4
Per review: drop the cross-namespace label-selector approach. Each app now carries its own VMPodScrape next to its redis/valkey manifests, selecting on the deployment's existing pod labels (mirroring the arrstack exportarr pattern), so no opt-in monitoring.unkin.net/redis-exporter label is needed. - Remove the monitoring.unkin.net/redis-exporter pod label from the artifactapi/authentik/litellm redis and gitea/netbox valkey deployments - Delete apps/base/observability/vmpodscrape-redis.yaml - Add a local-namespace VMPodScrape (port metrics, path /metrics) to artifactapi, authentik, litellm (app=redis), gitea (app=gitea-valkey), netbox (app=netbox-valkey), and jellyfin (valkey-operator node labels)
17 lines
482 B
YAML
17 lines
482 B
YAML
---
|
|
# Scrape the redis_exporter sidecar (:9121) on the netbox-valkey pod. Picked up
|
|
# by the observability VMAgent (selectAllByDefault). Pod-level rather than
|
|
# VMServiceScrape because the valkey Service doesn't expose the metrics port.
|
|
apiVersion: operator.victoriametrics.com/v1beta1
|
|
kind: VMPodScrape
|
|
metadata:
|
|
name: valkey-exporter
|
|
namespace: netbox
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
app: netbox-valkey
|
|
podMetricsEndpoints:
|
|
- port: metrics
|
|
path: /metrics
|