The tags in logs and webhook notifications are gibberish because of hashing. For logs and notices, it'd be nice if had the option of using unhashed tags, so it's more readily understandable even by non-technical stakeholders what's being cleared.

Comments

SpaceGoat1701 created an issue. See original summary.

vvuksan-fastly’s picture

vvuksan-fastly commented

Tags in notices will correspond to what a cached object gets cached with and ultimately what gets purged. You can expose what tags/surrogate keys an object has been cached with by using the Fastly-Debug header e.g.

curl -HFastly-Debug:1 -v -o /dev/null

vvuksan-fastly’s picture

vvuksan-fastly commented
Status: Active » Closed (won't fix)