Skip to content

fix: Alert when TPP edge apply lag exceeds 30s - #337

Open
mattdjenkinson wants to merge 1 commit into
mainfrom
fix/266-tpp-apply-lag-slo
Open

fix: Alert when TPP edge apply lag exceeds 30s#337
mattdjenkinson wants to merge 1 commit into
mainfrom
fix/266-tpp-apply-lag-slo

Conversation

@mattdjenkinson

@mattdjenkinson mattdjenkinson commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Second point on #266 asked us to measure upstream→edge TrafficProtectionPolicy propagation and decide whether it needs an SLO. Generation-bump samples converge in ~1.5s on staging and ~3.3s on prod — well under a 30s budget — so this adopts that SLO and pages when an edge stays behind.

The alert watches the existing extension-server gauges (nso_extension_tpp_cache_generation vs nso_extension_tpp_applied_generation), aggregated per edge/policy so replica noise does not flap.

Env Sample Converged
staging nowaf-test ~1.2s
staging help-d9c5g5 ~1.6s
prod portfolio-lmpn0u ~3.3s
prod waf-test-3gsu2v ~2.1s

Test plan

  • promtool test rules on test/prometheus-rules/gateways/nso-slo-tests.yaml (lag / in-sync / brief-skew)
  • Confirm rule lands in the cluster that scrapes edge envoy-gateway-extension-server metrics (same path as TLS extension alerts)
  • After deploy, verify no standing firings while the fleet is converged (cache > applied is empty today)

Related to #266.

Measured upstream→edge TPP generation convergence is ~1.5s in
staging and ~3.3s in prod. Adopt a 30s SLO (~10x headroom) and alert
when cache generation stays ahead of applied generation on an edge.

Key features:
- TrafficProtectionPolicyApplyLagSLOViolation on nso_extension_tpp_*
  generation gauges, aggregated per cluster/policy
- promtool coverage for lag, in-sync, and brief-skew cases

Related to #266.
@mattdjenkinson mattdjenkinson self-assigned this Aug 7, 2026
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