Skip to content

feat(aztec-node): add monitoring and central monitoring support#177

Open
bussyjd wants to merge 1 commit intomainfrom
feat/aztec-central-monitoring
Open

feat(aztec-node): add monitoring and central monitoring support#177
bussyjd wants to merge 1 commit intomainfrom
feat/aztec-central-monitoring

Conversation

@bussyjd
Copy link
Contributor

@bussyjd bussyjd commented Dec 18, 2025

Add two-tier monitoring configuration to the aztec-node helm chart, following the same pattern as the dv-pod chart for central monitoring.

Changes

New Configuration Options

monitoring.enabled - Deploys local monitoring stack:

  • OTEL collector (receives OTLP data from Aztec nodes, exposes Prometheus metrics on :8889)
  • Prometheus (scrapes OTEL collector, exposes :9090 for local queries)

centralMonitoring.enabled - Adds remote_write to Obol central endpoint:

  • Automatically enables the monitoring stack
  • Configures Prometheus remote_write to vm.monitoring.gcp.obol.tech/write
  • Requires authentication token

Behavior Matrix

monitoring.enabled centralMonitoring.enabled Result
false false No monitoring deployed
true false Local monitoring only (Prometheus on :9090)
false true Auto-enables monitoring + remote_write to central
true true Same as above

Usage

# Local monitoring only
helm upgrade ... --set monitoring.enabled=true

# Central monitoring (auto-enables local stack)
helm upgrade ... --set centralMonitoring.enabled=true \
  --set-string centralMonitoring.token="your-token"

Files Added

  • templates/otel-collector-configmap.yaml
  • templates/otel-collector-deployment.yaml
  • templates/otel-collector-service.yaml
  • templates/prometheus-configmap.yaml
  • templates/prometheus-deployment.yaml
  • templates/prometheus-service.yaml
  • templates/validate.yaml

Files Modified

  • values.yaml - Added monitoring and centralMonitoring sections
  • templates/statefulset.yaml - Auto-configure OTEL endpoint
  • templates/statefulset-prover-*.yaml - Auto-configure OTEL endpoint for prover components

ticket: none

@bussyjd bussyjd requested a review from a team as a code owner December 18, 2025 15:09
Add two-tier monitoring configuration:

1. monitoring.enabled - Deploys local OTEL collector + Prometheus
   - OTEL collector receives OTLP data, exposes Prometheus metrics on :8889
   - Prometheus scrapes OTEL collector, exposes :9090 for local queries

2. centralMonitoring.enabled - Adds remote_write to Obol central endpoint
   - Automatically enables monitoring stack
   - Configures Prometheus remote_write to vm.monitoring.gcp.obol.tech/write
   - Requires authentication token

Usage:
  # Local monitoring only
  helm upgrade ... --set monitoring.enabled=true

  # Central monitoring (auto-enables local stack)
  helm upgrade ... --set centralMonitoring.enabled=true \
    --set-string centralMonitoring.token="your-token"
@bussyjd bussyjd force-pushed the feat/aztec-central-monitoring branch from a976eb4 to 0ff040e Compare December 18, 2025 15:11
@bussyjd bussyjd requested a review from apham0001 December 18, 2025 15:11
# -- https endpoint to obol central prometheus
promEndpoint: "https://vm.monitoring.gcp.obol.tech/write"
# -- The authentication token to the central prometheus
token: ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we have also the possibility to configure in secret?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants