Anomaly Detector is disabled
Hello, I have a big Table in which we have our TimeSeries data from various devices. Since not every device sends the same data we have a big schema of numeric columns that are not filled for every deviceId. Is that the reason why there is no Anomaly Detector in my EventHouse? In the schema I can see that columns for the data are int or real. Some columns are string, but that shoudn't be the reason, right? Has anyone faced the same issue?
How to fix a Bad shortcut name
Hi, I have (had) a shortcut in may KQL Database called "terminals". The shortcut was pointing to the wrong lakehouse, so I had to drop it and create again. However, every time I create it again it adds a counter to the shortcut name: "_1", "_2" and so on. It doesn't matter if the previous shortcut was already dropped, it stills add a counter. How can I fix this problem? If I wait between dropping the original shortcut and creating the new one, woult it solve the problem ? I already tried waiting, but it didn't work. I imagine it may be a matter of how long I need to wait - how long? Is there any other way to solve this? Kind Regards, Dennes
Copilot for EventHouse Queryset
Hi, RTI has introduced the preview feature of Copilot for the Eventhouse Queryset, but is there any way to automate the Copilot usage, via API endpoint or SDKs? The idea is to programmatically generate relevant and meaningful Kusto queries for business insights, from the tables and datasets present in the KQL DB in Eventhouse using Copilot. Thanks in advance!
DataFlow Gen 2 with KQL Engine Query URI as the destination
I'm trying to implement the Content Delivery Lifecycle using workspace Git integration- see https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration I need the destination of my Data Flow to automatically pick up the right KQL Engine instance + connection, here: I can make it pick up the cluster URI from a library variable as show above. However, the problem that I have is that the connection name does not populate (also shown above). When I run the Data Flow (in this state) I get the error below:
Issue creating a KQL materialized view
Hi, I'm testing an eventstream that reads source events from an Azure Event Hubs and write them into a KQL table. I've created successfully a KQL materialized view (using summarize and arg_max clauses) with the backfill=true option, without specifying the async clause, while the eventstream was active. After two days, for debug purposes, I've tried to create a parallel materialized view with a different name using the same KQL code and I've obtained this error: But firts it isn't required the async keyword. So, I've tried to create an async materialized view using .create async materialized-view with (backfill=true) mymaterview on table mytable an OperationId is shown but it doesn't appear any materialized views. Now, I don't understand because first it isn't necessary to specify the async keyword and then I need to write it. Then, I don't understand because an async materialized view doesn't appear. I don't understand because I cannot create a parallel clone materialized view with a different name. I hope that a materialized view, created with or without the back fill option, keep updating with new source event data without executing any alter action on it. Any helps to me, please? Many thanks
