fix: enable causal anomaly spine in demo #3782

Closed
mfreeman451 wants to merge 0 commits from work/3731-enable-causal-spine-demo into staging
Owner

Summary

  • wire Helm values for anomaly analysis consumer runtime envs
  • wire Helm values for capacity forecasting runtime envs and Oban cron settings
  • enable both paths in demo values so the anomaly/capacity UI has live producers to evaluate

Notes

  • The anomaly consumer still defaults to the proposal conservative otel.metrics.> subject set; sysmon/SNMP/flow can be widened after demo verifies the live OTEL path.
  • The seasonal_profiles table called out in #3731 is stale evidence against current code: current forecasting stores projections in platform.capacity_forecasts and applies seasonal modeling in CapacityForecasting.Model, without a seasonal_profiles table reference.

Refs #3731

Validation

  • helm lint helm/serviceradar -f helm/serviceradar/values-demo.yaml
  • helm template serviceradar helm/serviceradar -n demo -f helm/serviceradar/values-demo.yaml --show-only templates/core.yaml confirmed ANOMALY_ANALYSIS_CONSUMER_ENABLED=true and SERVICERADAR_CAPACITY_FORECASTING_ENABLED=true in the rendered demo core deployment
## Summary - wire Helm values for anomaly analysis consumer runtime envs - wire Helm values for capacity forecasting runtime envs and Oban cron settings - enable both paths in demo values so the anomaly/capacity UI has live producers to evaluate ## Notes - The anomaly consumer still defaults to the proposal conservative otel.metrics.> subject set; sysmon/SNMP/flow can be widened after demo verifies the live OTEL path. - The seasonal_profiles table called out in #3731 is stale evidence against current code: current forecasting stores projections in platform.capacity_forecasts and applies seasonal modeling in CapacityForecasting.Model, without a seasonal_profiles table reference. Refs #3731 ## Validation - helm lint helm/serviceradar -f helm/serviceradar/values-demo.yaml - helm template serviceradar helm/serviceradar -n demo -f helm/serviceradar/values-demo.yaml --show-only templates/core.yaml confirmed ANOMALY_ANALYSIS_CONSUMER_ENABLED=true and SERVICERADAR_CAPACITY_FORECASTING_ENABLED=true in the rendered demo core deployment
Author
Owner

Closing as a duplicate/no-op. PR #3776 already merged this exact branch into staging; current diff is +0/-0. #3731 should track demo verification of the merged #3776 change, not this duplicate PR.

Closing as a duplicate/no-op. PR #3776 already merged this exact branch into staging; current diff is +0/-0. #3731 should track demo verification of the merged #3776 change, not this duplicate PR.
mfreeman451 closed this pull request 2026-06-13 12:36:41 +00:00
Some checks failed
Golang Tests / test-go (push) Successful in 2m6s
lint / lint (push) Failing after 2m26s
Helm Lint / Helm Lint (pull_request) Successful in 28s
Secret Scan / gitleaks (pull_request) Successful in 38s
lint / lint (pull_request) Failing after 1m32s
Elixir Quality / Elixir Quality (pull_request) Failing after 11m20s
CI / build (pull_request) Successful in 15m16s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar!3782
No description provided.