Fix Observability Issues and Startup Probe Failure #70

Closed
devitq wants to merge 2 commits from fix-observability-issues-17959231904052988380 into feat/setup-observability-in-k8s
2 Commits
Author SHA1 Message Date
google-labs-jules[bot]anddevitq 47baaf8fce Fix observability issues and refactor metrics stack to ArgoCD
- Resolved "connection refused" on startup probe by explicitly mapping management.server.port in application.yaml.
- Adjusted startupProbe to a 70s window (10s delay + 12 * 5s) to accommodate application initialization.
- Externalized VictoriaMetrics stack (Operator, Single, Agent, Alert) into separate ArgoCD Application manifests.
- Removed bundled VictoriaMetrics templates from the MovieNight Helm chart.
- Configured vmagent with Kubernetes pod-based service discovery for metrics scraping.
- Ensured consistency between Helm values and externalized observability components.

Co-authored-by: devitq <118541411+devitq@users.noreply.github.com>
2026-05-23 00:30:37 +00:00
google-labs-jules[bot]anddevitq 2d6012866b Fix observability and startup probe issues
- Explicitly configure management port 8081 in application.yaml to resolve connection refused errors.
- Adjust startupProbe failure threshold and initial delay in Helm chart to allow for a one-minute startup time.
- Update vmagent to use Kubernetes pod discovery for metrics scraping, adding necessary RBAC Role and RoleBinding.
- Introduce 'json-logging' Spring profile for structured console logging in Kubernetes.
- Add support for VictoriaMetrics Operator CRDs (VMSingle, VMAgent, VMPodScrape) to leverage the existing operator in the cluster.
- Review and refine observability templates for better integration with the VictoriaMetrics stack.

Co-authored-by: devitq <118541411+devitq@users.noreply.github.com>
2026-05-23 00:05:16 +00:00