-
Notifications
You must be signed in to change notification settings - Fork 3.4k
az monitor log-analytics query incorrectly process multiline analytics-query parameter #29152
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamMonitoraz monitoraz monitoract-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.potential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamMonitoraz monitoraz monitoract-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.potential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
A mutli-line analytics query is stripped, only first line is taken into consideration, the rest of the query is ignored.
Related command
Errors
az monitor log-analytics queryreturns all the date from SignInLogsIssue script & Debug output
az monitor log-analytics queryreturns all the date from SignInLogsExpected behavior
the filter
where TimeGenerated > ago(30minutes)should be taken into consideration, also the limit etc.Environment Summary
Additional context
https://martin.rublik.eu/2024/06/11/az-cli-and-loganalytics.html you can find detailed information here, along with workaround for this issue.