Rediger

Del via

Process data from your event hub using Azure Stream Analytics

  • Artikel

The Azure Stream Analytics service makes it easy to ingest, process, and analyze streaming data from Azure Event Hubs, enabling powerful insights to drive real-time actions. You can use the Azure portal to visualize incoming data and write a Stream Analytics query. Once your query is ready, you can move it into production in only a few clicks.

Key benefits

Here are the key benefits of Azure Event Hubs and Azure Stream Analytics integration:

  • Preview data – You can preview incoming data from an event hub in the Azure portal.
  • Test your query – Prepare a transformation query and test it directly in the Azure portal. For the query language syntax, see Stream Analytics Query Language documentation.
  • Deploy your query to production – You can deploy the query into production by creating and starting an Azure Stream Analytics job.

End-to-end flow

Important

  • If you aren't a member of owner or contributor roles at the Azure subscription level, you must be a member of the Stream Analytics Query Tester role at the Azure subscription level to successfully complete steps in this section. This role allows you to perform testing queries without creating a stream analytics job first. For instructions on assigning a role to a user, see Assign AD roles to users.
  • If your event hub allows only the private access via private endpoints, you must have the Stream Analytics job joined to the same network so that the job can access events in the event hub.

  1. Sign in to the Azure portal.

  2. Navigate to your Event Hubs namespace and then navigate to the event hub, which has the incoming data.

  3. On the left navigation menu, expand Features, and select Process data, and then select Start on the Enable real time insights from events tile.

    Screenshot showing the Process data page with Enable real time insights from events tile selected.

  4. You see a query page with values already set for the following fields. If you see a popup window about a consumer group and a policy being created for you, select OK. You immediately see a snapshot of the latest incoming data in this tab.

    1. Your event hub as an input for the query.

    2. Sample SQL query with SELECT statement.

    3. An output alias to refer to your query test results.

      Screenshot showing the Query editor for your Stream Analytics query.

    • The serialization type in your data is automatically detected (JSON/CSV). You can manually change it as well to JSON/CSV/AVRO.

    • You can preview incoming data in the table format or raw format.

    • If your data shown isn't current, select Refresh to see the latest events.

    • In the preceding image, the results are shown in the table format. To see the raw data, select Raw

      Screenshot of the Input preview window in the result pane of the Process data page in the raw format.

  5. Select Test query to see the snapshot of test results of your query in the Test results tab. You can also download the results.

    Screenshot of the Input preview window in the result pane with test results.

    Write your own query to transform the data. See Stream Analytics Query Language reference.

  6. Once you tested the query and you want to move it in to production, select Create Stream Analytics job.

    Screenshot of the Query page with the Create Stream Analytics job link selected.

  7. On the New Stream Analytics job page, follow these steps:

    1. Specify a name for the job.

    2. Select your Azure subscription where you want the job to be created.

    3. Select the resource group for the Stream Analytics job resource.

    4. Select the location for the job.

    5. For the Event Hubs policy name, create a new policy or select an existing one.

    6. For the Event Hubs consumer group, create a new consumer group or select an existing consumer group.

    7. Select Create to create the Stream Analytics job.

      Screenshot showing the New Stream Analytics job window.

      Note

      We recommend that you create a consumer group and a policy for each new Azure Stream Analytics job that you create from the Event Hubs page. Consumer groups allow only five concurrent readers, so providing a dedicated consumer group for each job will avoid any errors that might arise from exceeding that limit. A dedicated policy allows you to rotate your key or revoke permissions without impacting other resources.

  8. Your Stream Analytics job is now created where your query is the same that you tested, and input is your event hub.

    Screenshot showing the Stream Analytics job page with a link to add an output.

  9. Add an output of your choice.

  10. Navigate back to Stream Analytics job page by clicking the name of the job in breadcrumb link.

  11. Select Edit query above the Query window.

  12. Update [OutputAlias] with your output name, and select Save query link above the query. Close the Query page by selecting X in the top-right corner.

  13. Now, on the Stream Analytics job page, select Start on the toolbar to start the job.

    Screenshot of the Start job window for a Stream Analytics job.

Access

Issue : User can't access preview data because they don’t have right permissions on the Subscription.

Option 1: The user who wants to preview incoming data needs to be added as a Contributor on Subscription.

Option 2: The user needs to be added as Stream Analytics Query tester role on Subscription. Navigate to Access control for the subscription. Add a new role assignment for the user as "Stream Analytics Query Tester" role.

Option 3: The user can create Azure Stream Analytics job. Set input as this event hub and navigate to "Query" to preview incoming data from this event hub.

Option 4: The admin can create a custom role on the subscription. Add the following permissions to the custom role and then add user to the new custom role.

Screenshots showing Microsoft.StreamAnalytics permissions page.

Streaming units

Your Azure Stream Analytics job defaults to three streaming units (SUs). To adjust this setting, select Scale on the left menu in the Stream Analytics job page in the Azure portal. To learn more about streaming units, see Understand and adjust Streaming Units.

Screenshots showing the Scale page for a Stream Analytics job.

Considerations when using the Event Hubs Geo-replication feature

Azure Event Hubs recently launched the Geo-Replication feature in public preview. This feature is different from the Geo Disaster Recovery feature of Azure Event Hubs.

When the failover type is Forced and replication consistency is Asynchronous, Stream Analytics job doesn't guarantee exactly once output to an Azure Event Hubs output.

Azure Stream Analytics, as producer with an event hub an output, might observe watermark delay on the job during failover duration and during throttling by Event Hubs in case replication lag between primary and secondary reaches the maximum configured lag.

Azure Stream Analytics, as consumer with Event Hubs as Input, might observe watermark delay on the job during failover duration and might skip data or find duplicate data after failover is complete.

Due to these caveats, we recommend that you restart the Stream Analytics job with appropriate start time right after Event Hubs failover is complete. Also, since Event Hubs Geo-replication feature is in public preview, we don't recommend using this pattern for production Stream Analytics jobs at this point. The current Stream Analytics behavior will improve before the Event Hubs Geo-replication feature is generally available and can be used in Stream Analytics production jobs.

Related content

To learn more about Stream Analytics queries, see Stream Analytics Query Language