Seq.App.Azure.EventHub 1.1.2

dotnet add package Seq.App.Azure.EventHub --version 1.1.2
NuGet\Install-Package Seq.App.Azure.EventHub -Version 1.1.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Seq.App.Azure.EventHub" Version="1.1.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Seq.App.Azure.EventHub --version 1.1.2
#r "nuget: Seq.App.Azure.EventHub, 1.1.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Seq.App.Azure.EventHub as a Cake Addin
#addin nuget:?package=Seq.App.Azure.EventHub&version=1.1.2

// Install Seq.App.Azure.EventHub as a Cake Tool
#tool nuget:?package=Seq.App.Azure.EventHub&version=1.1.2

Seq.App.Azure

Apps for the Seq event server. You can find installable versions of these by searching for the seq-app tag on NuGet.

Currently in this repository you'll find:

  • EventHub - send Seq events to an Azure Event Hub.

EventHub

The Seq.App.Azure.EventHub app can be used to send Seq events to an Azure Event Hub. Once sent, you have many options regarding how you handle your log data. One such option is Stream Analytics. You can utilize Azure Stream Analytics to transport your event hub data to various ouputs like Microsoft's Power BI. By sending your log data to Power BI, you can visualize your data in countless ways including dashboards, charts, cards, widgets, reports, and many more.

Stream Analytics and Power BI

The following section walks you through setting up Stream Analytics with a Event Hub input and a Power BI output.

1. Create a Service Bus

If you don't already have one, you'll need to create an Azure Service bus to house the Event Hub.

Create Service Bus

2. Event Hub

2a. Create Event Hub

Now you can create your Event Hub. Name it whatever you like and is available. It should be something meaningful to your project/application.

Create Event Hub

2b. Configure a Shared Access Policy

Once the Event Hub is created, go over to the Configure tab and create a Share Access Policy. This allows you to generate a connection string and send events to the hub. You'll just need Send permissions.

Configure Shared Access Policy

2c. Connection String

Now go back to the Event Hub Dashboard and get the connection string by clicking View Connection String then copy it to your clipboard.

Event Hub Connection String

3. Configure Seq App

Next you'll need to configure the EventHub app in Seq. Go to Settings->Apps and click Start New Instance under Azure Event Hub and set the properties similar to the following:

Configure Seq App

Once created, go back into the app instance and click the View events raised by this instance link to verify that it's working properly.

Verify Seq App

4. Stream Analytics

4a. Create Job

Now that you've verified that Seq is sending events to your Event Hub it's time to create a Stream Analytics job.

Create Stream Analytics Job

4b. Add Input

Create an input for the Stream Analytics job. The input will be the Event Hub you just created and are now sending Seq events to.

Add Input - Step 1

Add Input - Step 2

Add Input - Step 3

Add Input - Step 4

4c. Add Output

Add an output. For this example you'll create a Power BI output like so:

Add Output - Step 1

Add Output - Step 2

Add Output - Step 3

4d. Create Query

Finally, create a Stream Analytics query to transfer data from the event hub to the Power BI output.

Create Query

5. Power BI

5a. Dataset

Once Stream Analytics starts sending data to Power BI, the dataset will be automatically created for you as you can see below:

Dataset

Click on the auto created data set to create a report:

Create Report

Click the thumbtack to save the report and pin it to your dashboard:

Pin to Dashboard

5b. Dashboard

Now you can view your report on the dashboard!

Dashboard

Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.1.2 219 10/31/2023
1.1.1 479 6/10/2022
1.1.0 428 6/10/2022
1.0.15 1,174 3/21/2017
1.0.14 933 3/21/2017
1.0.13 937 3/21/2017
1.0.12 957 3/21/2017
1.0.11 918 3/20/2017
1.0.10 993 3/20/2017
1.0.9 898 3/20/2017
1.0.8 922 3/20/2017
1.0.7 944 10/13/2016
1.0.6 945 10/13/2016
1.0.5 988 8/30/2016
1.0.4 1,019 4/11/2016
1.0.3 951 4/11/2016
1.0.2 1,009 4/6/2016
1.0.1 969 4/4/2016
1.0.0 986 4/4/2016

1.1.2 - Fix for duplicate property names
     1.1.0 - Upgrade to .NET 5
     1.0.15 - Remove field that has the same name as a static property
     1.0.14 - Remove fields that are configured as tags
     1.0.13 - Fixed another issue with tags
     1.0.12 - Fixed issue with tags
     1.0.11 - Force tags to be tags
     1.0.10 - Allow exclude/ignore properties from the data type specification
     1.0.9 - Added a way to force the data type for properties
     1.0.8 - Added trigger processing and updated dependencies
     1.0.7 - Added batching of messages and tag properties
     1.0.6 - Performance optimizations
     1.0.5 - Upgraded to Serilog 2.2.1