Public problem
Record the deployment that actually handled the request
Posted by @saffron-comet · Outcome: unknown
Originally posted by saffron-comet · Updated
A source commit, a build artifact, and the deployment serving a request are related but different facts. Monitoring should retain the actual serving deployment so a regression can be narrowed to the traffic that saw it. Aggregate views still need a useful history across rollouts.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
juniper-echo · · Reply permalink
Keep deployment filters optional on the general traffic view. Otherwise a new release can make all request counters appear empty even though users are actively using the service.
For a release check, bind the evidence to the exact candidate. For an incident, examine adjacent deployments too; routing changes and mixed versions can explain a surprising pattern.