ערוך

שתף באמצעות


Add an Eventhouse destination to an eventstream

This article shows you how to add an Eventhouse as a destination to an eventstream in Microsoft Fabric event streams.

Note

If you want to use enhanced capabilities that are in preview, select Enhanced capabilities at the top. Otherwise, select Standard capabilities. For information about enhanced capabilities that are in preview, see Introduction to Fabric event streams.

Prerequisites

  • Access to the Fabric premium workspace where your eventstream is located with Contributor or higher permissions.
  • Access to an Eventhouse created in a Fabric premium workspace where you have Contributor or higher permissions.

Note

The maximum number of sources and destinations for one eventstream is 11.

Add an Eventhouse as a destination

To add an Eventhouse as a destination, you can choose between two ingestion modes: Direct ingestion or Event processing before ingestion.

Direct ingestion mode

Direct ingestion mode ingests your event data directly into the Eventhouse without any processing. You can use direct ingestion mode to add an Eventhouse destination to your default stream.

Important

You can use Direct ingestion only for your default stream. Direct ingestion can't follow processing operators or derived streams. If you want to add a Eventhouse destination after processing operators or derived streams, use Event processing before ingestion instead.

  1. In Edit mode for your eventstream, select Add destination on the ribbon or select the Transform events or add destination card on the canvas, and then select Eventhouse.

    A screenshot of selecting Eventhouse in the Add destination dropdown list.

  2. On the Eventhouse screen, select Direct ingestion.

  3. Enter a Destination name, a Workspace, and a Eventhouse from the selected workspace.

  4. Select Save.

    A screenshot of the Eventhouse configuration screen.

  5. Connect the new Eventhouse destination card to the output of your eventstream if not already connected, and then select Publish.

    A screenshot of the eventstream with the Publish button highlighted.

  6. In Live view, select Configure in the KQL Database destination node.

    A screenshot of the published eventstream with the Configure button in the KQL Database destination highlighted.

  7. Your KQL Database opens in the Get data screen. Select an existing table of the KQL database, or select New table to create a new one to route and ingest the data.

  8. Provide a Data connection name or keep the name provided, and then select Next. It can take a few minutes to pull data from the eventstream.

    A screenshot of the Get data screen for the KQL Database destination, with the Next button highlighted.

  9. On the Inspect the data screen, you can:

    • Select a Format to preview how the data is sent to your KQL database.
    • Select Edit columns to configure the columns for your data.
    • Select Advanced to select events to include or to choose mapping options.

    A screenshot showing the data formats and Advanced options on the Inspect the data screen.

  10. If you select Edit columns, on the Edit columns screen you can:

    • Select Add column to add a column.
    • Select Source columns to map.
    • Apply Mapping transformation to columns.
    • Change Sample data values.

    Then select Apply.

    A screenshot of the Edit columns screen.

  11. When you're finished configuring the data, select Finish on the Inspect the data screen.

  12. On the Summary screen, review the details and status of your data ingestion, including the table with the schema you defined and the connection between the eventstream and the KQL database. Select Close to finalize the KQL database setup.

    A screenshot of the Summary screen with the Close button highlighted.

You can now see the KQL Database destination on the canvas in Live view.

A screenshot of the configured KQL Database destination in Live view.

Event processing before ingestion

The event processing before ingestion mode processes your event data before ingesting it into the KQL database. Use this mode if you apply operators such as filtering or aggregation to process the data before ingestion, or after a derived stream.

  1. In Edit mode for your eventstream, hover over an operator or derived stream, select +, and then select KQL Database.

    A screenshot of selecting the + symbol for the operator output and selecting KQL Database.

  2. On the KQL Database screen, Event processing before ingestion should already be selected. Complete the rest of the information about your KQL database, and then select Save.

    A screenshot of the KQL Database configuration screen for Event processing before ingestion.

  3. To implement the newly added KQL Database destination, select Publish.

    A screenshot of the eventstream in Edit mode with the KQL Database destination added.

Once you complete these steps, the eventstream with KQL Database destination is available for visualization in Live view.

A screenshot of the configured KQL Database event processing flow in Live view.

To learn how to add other destinations to an eventstream, see the following articles:

Prerequisites

Before you start, you must complete the following prerequisites:

  • Get access to a premium workspace with Contributor or above permissions where your eventstream is located.
  • Access to a premium workspace with Contributor or above permissions where your KQL database is located.

Note

The maximum number of sources and destinations for one eventstream is 11.

Add a KQL database as a destination

To add a KQL database as a destination, you need to have a KQL database created in the workspace, and choose between two ingestion modes: Direct ingestion and Event processing before ingestion.

Direct ingestion

This mode ingests your event data directly into the KQL database without any processing. You can use this mode if you want to ingest your event data as-is and perform any processing or transformation later in KQL database using KQL queries.

  1. Select New destination on the ribbon or "+" in the main editor canvas and then select KQL Database. The KQL Database destination configuration screen appears.

  2. Select Direct ingestion, enter a destination name, select a workspace, choose a KQL database from the selected workspace, and then select Add and configure.

    Note

    You can only select workspaces that have the same region Fabric capacity as the eventstream.

    Screenshot of the KQL Database pull mode destination configuration screen.

  3. On the Get data page, navigate through the tabs to complete the configuration:

    1. Configure: Use an existing table of your KQL database or create a new one to route and ingest the data. Complete the required fields and select Next.

      Screenshot showing the Destination tab of the Ingest data screen for creating a KQL database destination.

    2. Inspect: Select a data format, and preview how the data is sent to your KQL database.

      Screenshot showing the data format of the Ingest data screen for creating a KQL database destination.

      You can also change the column name, data type, or update column by clicking the arrow in the table header. Complete the required fields and select Finish.

      Screenshot showing how to change the column of the Ingest data screen for creating a KQL database destination.

      Screenshot showing the change the column name, data type of the Ingest data screen for creating a KQL database destination.

    3. Summary: Review the status of your data ingestion, including the table created with the schema you defined, and connection between the eventstream and the KQL database.

      Screenshot showing the Summary tab of the Ingest data screen for creating a KQL database destination.

  4. After you configure everything and select Close, a KQL database destination appears on the canvas, connected to your eventstream.

    Screenshot showing the new KQL database pull mode destination.

Event processing before ingestion

This mode processes your event data before ingesting it into the KQL database. You can use this mode if you want to apply some processing or transformation to your event data before ingesting it, such as filtering, aggregating, or expanding. You can design the processing logic using event processor.

  1. Select Event processing before ingestion, complete the information about your KQL Database, and then select Open event processor.

    Screenshot of the KQL Database push mode destination configuration screen.

  2. Design the event processing with event processor, and then select Save

    Screenshot of the push mode event processor screen.

  3. When you choose an existing Kusto table, schema validation between the current schema in this eventstream and the target KQL table is performed. If the two schemas aren't matched, an error message is shown and reminds you to open event processor to adjust the schema in this eventstream accordingly.

    Screenshot of the push mode event processor error screen.

    When you open the event processor, the detailed mismatch information is shown in Authoring error tab.

    Screenshot of the push mode event processor mismatch information screen.

  4. After you configure everything and select Save, a KQL database destination appears on the canvas, connected to your eventstream, and you can check the metrics in the Data insights and logs in Runtime logs.

    Screenshot showing the new KQL database push mode destination.

Manage a destination

Edit/remove: You can edit or remove an eventstream destination either through the navigation pane or canvas.

When you select Edit, the edit pane opens in the right side of the main editor. You can modify the configuration as you wish, including the event transformation logic through the event processor editor.

Screenshot showing where to select the modify and delete options for destinations on the canvas.

To learn how to add other destinations to an eventstream, see the following articles: