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?Eventhouse Capacity Planner minimum CU not reflected in UI/API
Hi all, We've set a minimum of 32 CU on our Eventhouse via Capacity Planner (autoscale alone isn't sufficient - we need guaranteed baseline capacity to protect a large bulk-ingestion workload from destination-side OutOfMemory during a migration). We've been told the 32 CU setting has been applied on the backend, but the Fabric UI and REST API (.show cluster / .show diagnostics) still report capacity/behavior consistent with a much lower tier. Can anyone confirm: Whether the a custom minimum CU value is actually enforced server-side even though the UI/API don't show it, and When UI/API reporting is expected to catch up to reflect the configured minimum? Any insight or similar experience would be appreciated.Fabric Business Events: what delivery guarantees and replay pattern should we design for?
Hi all, I am testing the newer Business Events capability in Fabric Real-Time Intelligence and trying to understand what reliability assumptions should be made for a production design. The pattern I am looking at is roughly: Eventstream → Business Event → Activator → downstream action / User Data Function with Eventhouse enabled so the published business events are also retained for historical analysis. The current documentation explains the publisher/consumer model and shows how Eventstream can publish a governed business event that Activator then consumes. What I have not been able to find clearly documented is the delivery contract between the published business event and its consumers. A few things I am trying to clarify: If an Activator consumer or downstream action is temporarily unavailable, does Fabric retry delivery of the business event? Should consumers assume at-least-once delivery and therefore be designed to handle duplicate events, or is a different delivery model used? Is event ordering guaranteed in any scope, for example for events from the same Eventstream publisher? Since published business events can also be retained automatically in Eventhouse, is that retained history intended to support replay/reprocessing after a consumer outage, or is it primarily an analytical record and replay would need to be implemented separately? Are there documented retry or delivery-retention windows that should be considered when designing an operational workflow? I am mainly trying to understand what a resilient production pattern should look like when the business event triggers something with side effects, where processing the same event twice or silently missing an event would matter. Would you generally make the downstream consumer idempotent and treat Eventhouse as an audit/recovery store, or is there a more Fabric-native pattern for this? Interested to hear how others are approaching this with Business Events and Activator.
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!
Real‑Time Dashboards cannot be created
Hi all. We’re currently facing an issue in the a Fabric tenant that prevents us from creating Real‑Time Dashboards. According to Microsoft documentation, this feature requires either a Fabric Premium capacity or a Premium Per User (PPU) license. Reference: Create a Real-Time Dashboard - Microsoft Fabric | Microsoft Learn For example: In one tenant (F4 capacity, North Europe) with a user licensed as Premium Per User, the feature works as expected. In another tenant (F16 capacity, Southeast Asia) with a user licensed as Pro, Real‑Time Dashboards cannot be created. The error shown is: “Real‑Time Dashboard item can only be created if this action is enabled in the tenant. Ask your tenant admin to enable this.” This error is confusing, as the option to enable the feature is no longer available in the Admin Portal. Anyone had a similar issue?
