For an ideal Canary deployment scenario, there should be 1+ Azure DevOps deployment gates which connects to the monitoring source related to the application health to determine whether or not to proceed with the next phase of deployment (i.e. to increase canary % of traffic or deploy from staging to prod).
For an ideal Canary deployment scenario, there should be 1+ Azure DevOps deployment gates which connects to the monitoring source related to the application health to determine whether or not to proceed with the next phase of deployment (i.e. to increase canary % of traffic or deploy from staging to prod).
To best accomplish this, a Prometheus deployment gate extension should be created which is similar to the Azure monitor deployment gate extension. This would query the Prometheus API.
Related articles: https://docs.microsoft.com/en-us/azure/azure-monitor/app/continuous-monitoring https://github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/authoring/gates.md https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/azure-monitor?view=azure-devops https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/index?view=azure-devops