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

[FEATURE REQ] - Introduce a way to instrument ARM calls from APIOps with a specific user-agent header #386

Closed
waelkdouh opened this issue Sep 15, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@waelkdouh
Copy link
Contributor

Please describe the feature.

We could set the User-Agent header to include "APIOps" (ideally at the start of the header, so the queries are more performant) and potentially even the version of APIOps. The User-Agent header is logged as a column in Kusto for all ARM logs, so we could then easily filter by it. We just need to watch out to make sure that SDKs, or whatever we are using for API calls, don't override this header.

Lets make sure we include a disclaimer following the guidance discussed here. Alternatively, we could just mention that we set this header to better understand the use of APIOps, but there's no personal data (PII) logged or captured - it would only allow us to see which API Management services use APIOps.

@waelkdouh waelkdouh added the enhancement New feature or request label Sep 15, 2023
@waelkdouh waelkdouh moved this to 📋 Backlog in APIOPS Roadmap Sep 15, 2023
@Azure Azure deleted a comment from github-actions bot Sep 15, 2023
@guythetechie guythetechie moved this from 📋 Backlog to 👀 In review in APIOPS Roadmap Apr 30, 2024
@waelkdouh waelkdouh moved this from 👀 In review to ✅ Done in APIOPS Roadmap Jul 3, 2024
@mikebudzynski
Copy link

We now have telemetry to better understand usage of various APIOps versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

3 participants