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
The Azure Monitor Log Analytics service team stores the caller information for their REST APIs. To support tracking HTTP requests from the Azure Monitor Query library, send an x-ms-app request header. The header's value should be set to AzureMonitorQuerySDK. The metrics team uses the user agent to identify the caller. Send this header ONLY for logs queries.
The text was updated successfully, but these errors were encountered:
After reviewing with the arch board, a decision was made to not make this change. As a workaround, the Draft service team can run a contains operation on the user agent string to identify the caller. This workaround has been communicated to Dan Hadari.
[Hub Generated] Review request for Microsoft.Peering to add version stable/2022-10-01 (Azure#21196)
* Adds base for updating Microsoft.Peering from version stable/2022-06-01 to version 2022-10-01
* Updates readme
* Updates API version in new specs and examples
* update peering api version
* update peering api version
* fixing resource inheritance
* making readme.md consistent with previous versions
* lint diff fix
* fixing serialization for examples
Library name
@azure/monitor-query
Please describe the feature.
The Azure Monitor Log Analytics service team stores the caller information for their REST APIs. To support tracking HTTP requests from the Azure Monitor Query library, send an
x-ms-app
request header. The header's value should be set toAzureMonitorQuerySDK
. The metrics team uses the user agent to identify the caller. Send this header ONLY for logs queries.The text was updated successfully, but these errors were encountered: