Skip to content

Commit dfd4e16

Browse files
committed
adding more details about EH data explorer
1 parent 663ac92 commit dfd4e16

File tree

1 file changed

+22
-1
lines changed

1 file changed

+22
-1
lines changed

articles/event-hubs/event-hubs-data-exploer.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,25 @@ ms.date: 08/22/2024
77

88
Azure Event Hubs is a scalable event processing service that ingests and processes large volumes of events and data, with low latency and high reliability. For a high-level overview of the service, see [What is Event Hubs?](event-hubs-about.md).
99

10-
This article highlights the functionality of Azure Event Hubs Data explorer, that is made available on the Azure portal.
10+
Developers and Operators are often looking for an easy tool to send sample data to their Event Hub to test the end-to-end flow, or view events at a specific offset (or point in time) for light debugging, often after the fact. The Event Hubs Data Explorer makes these common workflows simple by eliminating the need to write bespoke client applications to test and inspect the data on the event hub.
11+
12+
This article highlights the functionality of Azure Event Hubs Data explorer, that is made available on the Azure portal.
13+
14+
Operations run on an Azure Event Hubs namespace are of two kinds.
15+
16+
* Management Operations - Create, update, delete of Event Hubs namespace, and topics.
17+
* Data Operations - Send and view events from an event hub.
18+
19+
> [!IMPORTANT]
20+
> * The Event Hubs Data Explorer doesn't support **management operations**. The event hub must be created before the data explorer can send or view events from that event hub.
21+
> * While events payloads (known as **values** in Kafka) sent using the **Kafka protocol** will be visible via the data explorer, the **key** for the specific event will not be visible.
22+
> * We advice against using the Event Hubs Data Explorer for larger messages, as this may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
23+
>
24+
25+
# Prerequisites
26+
27+
To use the Event Hubs Data Explorer tool, [create an Azure Event Hubs namespace and an event hub](event-hubs-create.md).
28+
29+
# Use the Event Hubs Data Explorer
30+
31+
To use

0 commit comments

Comments
 (0)