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
-[Example of handling response](#example-of-handling-response)
@@ -122,7 +124,7 @@ Each set of metric values is a time series with the following characteristics:
122
124
123
125
The `LogsQueryClient` can be used to query a Log Analytics workspace using the [Kusto Query Language][kusto_query_language]. The `timespan.duration` can be specified as a string in an ISO 8601 duration format. You can use the `Durations` constants provided for some commonly used ISO 8601 durations.
124
126
125
-
You can query logs by workspace ID or resource ID. The result is returned as a table with a collection of rows.
127
+
You can query logs by Log Analytics workspace ID or Azure resource ID. The result is returned as a table with a collection of rows.
126
128
127
129
#### Workspace-centric logs query
128
130
@@ -841,7 +843,10 @@ Each Azure resource must reside in:
841
843
- The same region as the endpoint specified when creating the client.
842
844
- The same Azure subscription.
843
845
844
-
Furthermore, the metric namespace containing the metrics to be queried must be provided. For a list of metric namespaces, see [Supported metrics and log categories by resource type][metric_namespaces].
846
+
Furthermore:
847
+
848
+
- The user must be authorized to read monitoring data at the Azure subscription level. For example, the [Monitoring Reader role](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/monitor#monitoring-reader) on the subscription to be queried.
849
+
- The metric namespace containing the metrics to be queried must be provided. For a list of metric namespaces, see [Supported metrics and log categories by resource type][metric_namespaces].
0 commit comments