The solution architecture is illustrated below. During deployment, 90 days of events were generated and stored in the Fabric EventHouse database. After the deployment, the `Telemetry Data Simulator` can be invoked at any time to generate real-time events. Please refer to [Event Simulator Guide](./EventSimulatorGuide.md) for details on the usage. The real-time data is ingested into Event Hub which sends the data to Fabric EventStream. The EventStream ingests data into EventHouse. The `events` table in the EventHouse database hosts combined historical data and real-time data, which is used by the real-time intelligence dashboard via Kusto Query Language (KQL) queries. The EventStream data is also fed into the Activator. The Activator has built-in intelligence to detect anomalies and send notifications via email. The notification can also be configured to send alerts to a specific Teams Channel. For more information, please refer to [Activator Guide](./ActivatorGuide.md).
0 commit comments