User Profile
loadedlouie270
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Azure SQL Database - Diagnostic Settings - Possible Bug
Hi, so when configuring the Diagnostic Settings for a azure SQL databatabe if we select "all logs", 2 new options for diagnostic settings pop up. In the following image, first, you see without checking the "all Logs" checkbox on the left, in the middle of the image, you can see the 2 new logs showing, and on the right, you can see that it doesn't appear on the supposed logs available. I'm pretty sure this is a bug, can someone confirm this behavior. Thanks in advance, best regards.Deploying Azure Monitor Alert Rules by Pipeline gives error
Hi all, 🙂 Context: I'm deploying a ARM Template in a Azure Devops pipeline... The target is an Application Insights, and the query returns results. This ARM template works, and it's valid, it has been deployed on VisualStudio without a problem. But when I go to deploy the same ARM Template, on a pipeline in DevOps , I get the following error: -------------------------------------------------------------------- "error": { "message": "The request had some invalid properties", "code": "BadArgumentError", "correlationId": "", "innererror": { "code": "SemanticError", "message": "A semantic error occurred.", "innererror": { "code": "SEM0100", "message": "'where' operator: Failed to resolve column or scalar expression named 'timestamp'" } I deleted the correlation id value on purpose on the error up, its not missing 🙂 -------------------------------------------------------------------- I know that this error can be thrown by a non-existing Column, but this is not the case. The column exists on the table, and it's the equivalent to Timegenerated on LAW ... The query is the following: -------------------------------------------------------------------- dependencies |summarizeResponseDurationMS=percentile(duration,95)bytimestamp,operation_Name |whereResponseDurationMS>2000 |orderbyResponseDurationMSdesc -------------------------------------------------------------------- So I need some help. Not really sure if, the name "timestamp" used in the query, is also used on the pipeline by default/design somehow... and when parsed on a query, it needs "special" escapes caracter or something... like the \" per example. I tried to use column_ifexists(timestamp), without success....and even extend to a new column as a todate(), also without success... I can use and deploy the same template, if i just remove the timestamp from the query.... but, i really want the timestamp column there.. Any thoughts.? Thanks in advance to all ...
