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
| body | Logs everything in BASIC, plus all the request and response body. |
68
68
| body_and_headers | Logs everything in HEADERS and BODY. |
69
69
70
-
**NOTE**: When logging the body of request and response, please ensure that they do not contain confidential
71
-
information. When logging headers, the client library has a default set of headers that are considered safe to log
70
+
**NOTE**: When logging the body of request and response, please ensure that they do not contain confidential
71
+
information. When logging headers, the client library has a default set of headers that are considered safe to log
72
72
but this set can be updated by updating the log options in the builder as shown below:
73
73
74
74
```java
@@ -89,34 +89,32 @@ for more details on the various types of credential supported in `azure-identity
89
89
90
90
### Troubleshooting insufficient access error
91
91
92
-
If you get an HTTP error with status code 403 (Forbidden), it means that the provided credentials does not have
93
-
sufficient permissions to query the workspace.
92
+
If you get an HTTP error with status code 403 (Forbidden), it means that the provided credentials does not have
93
+
sufficient permissions to query the workspace.
94
94
```text
95
95
com.azure.core.exception.HttpResponseException: Status code 403, "{"error":{"message":"The provided credentials have insufficient access to perform the requested operation","code":"InsufficientAccessError","correlationId":""}}"
96
-
97
96
at com.azure.monitor.query/com.azure.monitor.query.LogsQueryAsyncClient.lambda$queryWorkspaceWithResponse$7(LogsQueryAsyncClient.java:346)
98
97
```
99
98
100
99
1. Check that the application or user that is making the request has sufficient permissions:
101
100
* You can refer to this document to [manage access to workspaces](https://docs.microsoft.com/azure/azure-monitor/logs/manage-access#manage-access-using-workspace-permissions)
102
-
2. If the user or application is granted sufficient privileges to query the workspace, make sure you are
103
-
authenticating as that user/application. If you are authenticating using the
101
+
2. If the user or application is granted sufficient privileges to query the workspace, make sure you are
102
+
authenticating as that user/application. If you are authenticating using the
If you get an HTTP error with status code 400 (Bad Request), you may have an error in your Kusto query and you'll
109
+
If you get an HTTP error with status code 400 (Bad Request), you may have an error in your Kusto query and you'll
111
110
see an error message similar to the one below.
112
111
113
112
```text
114
113
com.azure.core.exception.HttpResponseException: Status code 400, "{"error":{"message":"The request had some invalid properties","code":"BadArgumentError","correlationId":"ff3e2a7e-e95c-4437-82cf-9b15761d0850","innererror":{"code":"SyntaxError","message":"A recognition error occurred in the query.","innererror":{"code":"SYN0002","message":"Query could not be parsed at 'joi' on line [2,244]","line":2,"pos":244,"token":"joi"}}}}"
115
-
116
114
at com.azure.monitor.query/com.azure.monitor.query.LogsQueryAsyncClient.lambda$queryWorkspaceWithResponse$7(LogsQueryAsyncClient.java:346)
117
115
```
118
116
119
-
The error message may include the line number and position where the Kusto query has an error (line 2, position 244
117
+
The error message may include the line number and position where the Kusto query has an error (line 2, position 244
120
118
in the above example). You may also refer to the [Kusto Query Language](https://docs.microsoft.
121
119
com/en-us/azure/data-explorer/kusto/query/) reference docs to learn more about querying logs using KQL.
0 commit comments