monitoring: workers serve no metrics; scrape backend only

This commit is contained in:
planpal 2026-09-02 15:38:09 +07:00
parent a9bb6ff4fc
commit ae91a52a17

View File

@ -60,11 +60,13 @@ apps:
hpa: { min: 2, max: 5, cpu: 50 } hpa: { min: 2, max: 5, cpu: 50 }
pdb: { maxUnavailable: 1 } pdb: { maxUnavailable: 1 }
# Workers declare no metrics port: the worker binaries don't serve /metrics
# (only planpal-server does). Adding one just yields a DOWN scrape target.
schedule-worker: schedule-worker:
command: [planpal-schedule-worker] command: [planpal-schedule-worker]
image: backend image: backend
envFrom: [backend-env, aws-env] envFrom: [backend-env, aws-env]
ports: [{ name: metrics, containerPort: 9091 }] ports: []
resources: resources:
requests: { cpu: 25m, memory: 64Mi } requests: { cpu: 25m, memory: 64Mi }
limits: { cpu: 200m, memory: 256Mi } limits: { cpu: 200m, memory: 256Mi }
@ -74,7 +76,7 @@ apps:
command: [planpal-notification-worker] command: [planpal-notification-worker]
image: backend image: backend
envFrom: [backend-env, aws-env] envFrom: [backend-env, aws-env]
ports: [{ name: metrics, containerPort: 9092 }] ports: []
resources: resources:
requests: { cpu: 25m, memory: 64Mi } requests: { cpu: 25m, memory: 64Mi }
limits: { cpu: 200m, memory: 256Mi } limits: { cpu: 200m, memory: 256Mi }
@ -84,7 +86,7 @@ apps:
command: [planpal-ai-worker] command: [planpal-ai-worker]
image: backend image: backend
envFrom: [backend-env, aws-env] envFrom: [backend-env, aws-env]
ports: [{ name: metrics, containerPort: 9093 }] ports: []
resources: resources:
requests: { cpu: 25m, memory: 64Mi } requests: { cpu: 25m, memory: 64Mi }
limits: { cpu: 200m, memory: 256Mi } limits: { cpu: 200m, memory: 256Mi }