Hi team, the policy step through debugging tool is awesome. It however, seems to be affected by the new behavior around tracing and debugging in APIM. We see this discussed in the tracing alert docs-include.
By visiting the subscription blade and enabling tracing on the subscription and then using that subscription key, the policy debugging is still usable however, the language used on the tracing alert suggests that the product team is moving away from using subscription-level tracing. Do you have any active communication w/ the product team to suggest that subscription-enabled tracing/debugging is still going to be available going forward which'd allow the policy-debugger to work despite their messaging which suggests api-level tracing enablement via REST API is recommended?
Hi team, the policy step through debugging tool is awesome. It however, seems to be affected by the new behavior around tracing and debugging in APIM. We see this discussed in the tracing alert docs-include.
By visiting the subscription blade and enabling tracing on the subscription and then using that subscription key, the policy debugging is still usable however, the language used on the tracing alert suggests that the product team is moving away from using subscription-level tracing. Do you have any active communication w/ the product team to suggest that subscription-enabled tracing/debugging is still going to be available going forward which'd allow the policy-debugger to work despite their messaging which suggests api-level tracing enablement via REST API is recommended?
Thanks!