Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How will the policy debugger feature be affected by the changes rolling out for API tracing? #363

Open
erikhjensen opened this issue Sep 4, 2024 · 0 comments

Comments

@erikhjensen
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant