The metadata tracer shows metadata applied to a URL of the current property version active either on staging or production. The tags of applied behaviors and criteria are highlighted in yellow. If a tag is not highlighted, it means that the behavior or criteria was not applied.
In the Stages section, you can see ✔︎ and ✘. ✔︎ means that the tag was successfully applied and executed in the metadata stage. ✘ means that the tag was successfully applied but failed to execute in the metadata stage, this scenario is very rare.
| Stage number | Metadata stage |
|---|---|
| 0 | client-request |
| 1 | client-request-body |
| 2 | ipa-response |
| 3 | cache-hit |
| 4 | forward-start |
| 5 | forward-request |
| 6 | forward-response |
| 7 | client-response |
| 8 | client-done |
| 9 | content-policy |
| 10 | forward-insufficient-response |
To learn more about stages themselves, check metadataStage.
Example 1
A user has set up the caching latest behavior for their property in Property Manager. This fragment of the results shows how it was applied to their property.
The settings that got successfully applied and executed are highlighted in yellow:
cache max-age,cache honor-expires,cache header-update.allow,cache must-revalidate, andassign variableon the 0 stage (client-request).cache no-storeandcache bypasson the 0 (client-request), 5 (forward-request), and 6 (forward-response).
Example 2
A user has set up the edgeSideIncludes latest behavior for their property in Property Manager. This fragment of the results shows how it was applied to their property.
Because none of the settings are highlighted, it means the behavior was not applied to the property and it needs to be reconfigured in Property Manager.