Search results
Jul 24, 2019 · I'm able to ingest data from an EventHub directly into my Azure Data Explorer (ADX) database. In my production case, the Eventhub is in a different subscription than the ADX cluster. A service principal is given access to the eventhub through the Data Receiver role.
May 2, 2019 · I've got some JSON data coming into an IOT Hub, which then triggers a function to un-nest the data. The function sends this data to an Event Hub, and then the data is supposed to be ingested by Azure Data Explorer according to the mapping I've set up.
May 17, 2017 · The event handler often lives in code that is far removed from yours, written by a programmer you never met before. You can change the EventArgs type, deriving your own and adding extra fields, that distant code will continue to work without it having to be recompiled.
Dec 17, 2015 · @stringo0 sender is the object that raised the event (it calls the event delegate by passing 'this' by convention). EventArgs, if not subclassed, is of totally no use. So unless you have a SelectedIndexEventArgs parameter or CancelEventArgs you can't do anything.
Aug 3, 2017 · EventIds are application specific so you can use whatever ranges you like. Just ensure you document what you have used and where so that you can ensure you don't use an id twice, or to facilitate easier debugging.
Feb 18, 2016 · CheckPoint : as of today - EventHubs only supports client-side check-pointing. When you call Checkpoint from your Client-code: - it will translate to a Storage call (directly from Client) - which will store the current offset in the storage account you provided.
Jul 29, 2012 · To understand event handlers, you need to understand delegates. In C#, you can think of a delegate as a pointer (or a reference) to a method. This is useful because the pointer can be passed around as a value. The central concept of a delegate is its signature, or shape. That is (1) the return type and (2) the input arguments.
