Edit

Share via


Add anomaly detection events to an eventstream (preview)

Anomaly detection events allow you to subscribe to anomalies detected in your Eventhouse data, and then react to those anomalies in real time. With Fabric event streams, you can capture these anomaly detection events, transform them, and route them to various destinations in Fabric for further analysis.

This article shows you how to add Anomaly detection events source to an eventstream.

Prerequisites

  • Get access to a workspace in the Fabric capacity license mode (or) the Trial license mode with Contributor or higher permissions.

Add Anomaly detection events as source

If you haven't added any source to your eventstream yet, select the Connect data sources tile. You can also select Add source > Connect data sources on the ribbon.

Screenshot that shows the selection of the tile for using an external source.

If you're adding the source to an already published eventstream, switch to Edit mode. On the ribbon, select Add source > Connect data sources.

Screenshot that shows selections for adding external sources.

On the Select a data source page, search for and select Connect on the Anomaly detection events tile.

Screenshot that shows the selection of Anomaly detection events as the source type in the Select a data source window from Eventstream.

Configure and connect to Anomaly detection events

  1. On the Connect page, for Event types, only Microsoft.Fabric.AnomalyEvents.AnomalyDetected is currently supported.

  2. If you want to review the Schemas for the event types before proceeding, select View selected event type schemas. You can browse the schemas for the events, and then return to the previous page by selecting the back arrow at the top.

    Screenshot that shows the selection of Anomaly detection events types on the Connect page.

  3. For Event scope, only By configuration is supported. After you select this option, select a workspace.

    Screenshot that shows the selection the event scope.

  4. Select an Anomaly detector Item and Configuration. Make sure that you published the configuration in the Anomaly Detector item.

    Screenshot that shows how to select the configuration.

  5. On the Configure connection settings page, optionally add filters to filter incoming anomaly detection events. To add a filter:

    1. Select + Filter.

    2. Select a field.

    3. Select an operator.

    4. Select one or more values to match.

      Screenshot that shows the addition of a filter.

Stream or source details

  1. On the Connect page, follow one of these steps based on whether you're using Eventstream or Real-Time hub.

    • Eventstream:

      In the Source details pane to the right, follow these steps:

      1. For Source name, select the Pencil button to change the name.

      2. Notice that Eventstream name and Stream name are read-only.

    • Real-Time hub:

      In the Stream details section to the right, follow these steps:

      1. Select the Fabric workspace where you want to create the eventstream.

      2. For Eventstream name, select the Pencil button, and enter a name for the eventstream.

      3. The Stream name value is automatically generated for you by appending -stream to the name of the eventstream. This stream appears on the real-time hub's All data streams page when the wizard finishes.

  2. Select Next at the bottom of the Configure page.

Review and connect

On the Review + connect screen, review the summary, and select Add (Eventstream) or Connect (Real-Time hub).

View updated eventstream

  1. Once the connection is created, you can see the Anomaly detection events source added to your eventstream in Edit mode. Select Publish to publish the eventstream and capture the Anomaly detection events.

    Screenshot that shows the edit mode in Eventstream.

  2. If you want to transform events from the Anomaly detection events source, open your eventstream and select Edit on the toolbar to enter Edit mode. Then you can add operations to transform the Anomaly detection events or route them to a destination such as Lakehouse.

    Screenshot that shows the live view in Eventstream.

Limitation

  • The Anomaly Detection events source currently doesn't support CI/CD features, including Git Integration and Deployment Pipeline. Attempting to export or import an Eventstream item with this source to a Git repository may result in errors.