Skip to content

Commit b1a9627

Browse files
authored
revert title
1 parent 97ca03e commit b1a9627

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/how-to-safely-rollout-online-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -318,7 +318,7 @@ Though `green` has 0% of traffic allocated, you can still invoke the endpoint an
318318

319319
---
320320

321-
## Shadow test the deployment with mirrored traffic
321+
## Test the deployment with mirrored traffic (preview)
322322
[!INCLUDE [preview disclaimer](../../includes/machine-learning-preview-generic-disclaimer.md)]
323323

324324
Once you've tested your `green` deployment, you can copy (or 'mirror') a percentage of the live traffic to it. Mirroring traffic doesn't change results returned to clients. Requests still flow 100% to the `blue` deployment. The mirrored percentage of the traffic is copied and submitted to the `green` deployment so you can gather metrics and logging without impacting your clients. Mirroring is useful when you want to validate a new deployment without impacting clients. For example, to check if latency is within acceptable bounds and that there are no HTTP errors. This kind of testing scenario is also known as shadow testing.

0 commit comments

Comments
 (0)