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
I ran the following, and there was an issue with the first diagnostic settings, as reported below:
PS C:\tools\azqr> azqr scan -o 20240131.results --debug
2024-01-31T08:57:03+13:00 DBG Debug logging enabled
2024-01-31T08:57:08+13:00 INF Scanning subscriptions/...fa0f7c1 for Private Endpoints
2024-01-31T08:57:09+13:00 INF Scanning subscriptions/...fa0f7c1 for Resource Ids
2024-01-31T08:57:11+13:00 INF Scanning subscriptions/...fa0f7c1 for Diagnostic Settings
2024-01-31T08:57:12+13:00 FTL Failed to get diagnostic settings error="unmarshalling type *scanners.ArmBatchResponse: unmarshalling type *armmonitor.DiagnosticSettingsResourceCollection: json: cannot unmarshal string into Go value of type map[string]json.RawMessage"
I can't find the debug log to share - no output file has been created.
The diagnostics settings are set by policy, using the EPAC framework.
Steps to Reproduce the Problem
Not sure of specifics - but consistently happens on the first diagnostic setting. Happy to be given more guidance to try.
The text was updated successfully, but these errors were encountered:
can you please set the AZURE_SDK_GO_LOGGING environment variable to all, run the tool with the --debug flag and then share the console output with us (mask any values you don't want to share).
Expected Behavior
Scans complete successfully
Actual Behavior
I ran the following, and there was an issue with the first diagnostic settings, as reported below:
I can't find the debug log to share - no output file has been created.
The diagnostics settings are set by policy, using the EPAC framework.
Steps to Reproduce the Problem
Not sure of specifics - but consistently happens on the first diagnostic setting. Happy to be given more guidance to try.
The text was updated successfully, but these errors were encountered: