Change Impact & Configuration Drift
How changes in one layer alter behavior in adjacent layers — and whether those effects are visible.
Identify recent deployments or configuration changes that correlate with shifts in latency, saturation, or error rate; include deployment metadata, config diffs, and dependency-level effects.
2. Which services show regressions after runtime or dependency configuration changes?Detect services showing performance or resource regressions after runtime, autoscaling, or dependency configuration changes; include before/after comparison across affected layers.
3. Where is configuration drift causing behavioral divergence across similar services?Identify configuration drift causing behavioral divergence across otherwise similar services or environments; include specific parameter differences and observed effect.
4. Which changes increased load on downstream systems without increasing top-line traffic?Identify changes that increased load on downstream systems without increasing top-line traffic. Examples: lower cache hit ratio causing more database calls, new retry behavior amplifying queue pressure, schema change increasing storage I/O.
5. Which services lack safe rollout controls relative to their blast radius?Identify services that lack safe rollout controls (canary, progressive delivery, automated rollback) relative to their dependency sensitivity and blast radius.