nxtgauge-gitops/ops/openobserve-alerts
Ashwin Kumar Sivakumar 37a589fa87 fix(backend): add PORT env to all rust deployments (was crashing on boot)
16 of 20 rust services had no PORT env var set; their main.rs calls
std::env::var('PORT').expect('PORT must be a valid u16') which panicked
on startup. This commit adds env.PORT matching the existing containerPort
for each service. Service ports: gateway=9100 users=9101 companies=9102
jobs=9103 job_seekers=9104 customers=9105 employees=9106 photographers=9107
tutors=9108 makeup_artists=9109 developers=9110 video_editors=9111
graphic_designers=9112 social_media_managers=9113 fitness_trainers=9114
catering_services=9115 payments=9116 ugc_content_creators=9117 leads=9118
2026-06-11 01:17:15 +05:30
..
configmap-additional.yaml fix(backend): add PORT env to all rust deployments (was crashing on boot) 2026-06-11 01:17:15 +05:30
configmap.yaml fix(backend): add PORT env to all rust deployments (was crashing on boot) 2026-06-11 01:17:15 +05:30
cronjob.yaml fix: run db migrations as Argo PreSync hook + add openobserve collector/alerts 2026-04-17 17:10:37 +05:30
kustomization.yaml fix: run db migrations as Argo PreSync hook + add openobserve collector/alerts 2026-04-17 17:10:37 +05:30
README.md fix: run db migrations as Argo PreSync hook + add openobserve collector/alerts 2026-04-17 17:10:37 +05:30

OpenObserve alerts + Telegram

This deploys a CronJob (openobserve-alerts-bootstrap) that upserts alert templates + common alerts in OpenObserve.

Prereqs

Create a Kubernetes Secret with your Telegram chat id:

kubectl -n openobserve create secret generic openobserve-telegram \
  --from-literal=TELEGRAM_CHAT_ID='<your_chat_id>'

The OpenObserve credentials are read from the existing Secret created by the OpenObserve install:

  • o2-openobserve-standalone (ZO_ROOT_USER_EMAIL, ZO_ROOT_USER_PASSWORD)

Notes

  • Alerts are created to send to destination nxtgauge_telegram (must exist in OpenObserve).
  • Edit ops/openobserve-alerts/configmap.yaml to add/remove alerts.