You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: