You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-node-get-started-send.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md
17
17
18
18
To complete this quickstart, you need the following prerequisites:
19
19
20
-
-**Microsoft Azure subscription**. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/) or use your MSDN subscriber benefits when you [create an account](https://azure.microsoft.com).
20
+
-**Microsoft Azure subscription**. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
21
21
- Node.js LTS. Download the latest [long-term support (LTS) version](https://nodejs.org).
22
22
- Visual Studio Code (recommended) or any other integrated development environment (IDE).
23
23
-**Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. To create a namespace and an event hub, follow the procedure in [this article](event-hubs-create.md).
@@ -139,16 +139,14 @@ In this section, you create a JavaScript application that sends events to an eve
139
139
---
140
140
141
141
1. Run `node send.js` to execute thisfile. This command sends a batch of three events to your eventhub. If you're using the Passwordless (Azure Active Directory's Role-based Access Control) authentication, you might want to run `az login` and sign into Azure using the account that was added to the Azure Event Hubs Data Owner role.
142
-
1. In the Azure portal, verify that the event hub has received the messages. Refresh the page to update the chart. It might take a few seconds for it to show that the messages have been received.
142
+
1. In the Azure portal, verify that the event hub received the messages. Refresh the page to update the chart. It might take a few seconds for it to show that the messages are received.
143
143
144
144
[](./media/node-get-started-send/verify-messages-portal.png#lightbox)
145
145
146
146
> [!NOTE]
147
147
> For the complete source code, including additional informational comments, go to the [GitHub sendEvents.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/event-hubs/samples/v5/javascript/sendEvents.js).
148
148
149
-
You have now sent events to an event hub.
150
-
151
-
149
+
152
150
## Receive events
153
151
In this section, you receive events from an event hub by using an Azure Blob storage checkpoint store in a JavaScript application. It performs metadata checkpoints on received messages at regular intervals in an Azure Storageblob. This approach makes it easy to continue receiving messages later from where you left off.
154
152
@@ -170,13 +168,13 @@ To create an Azure storage account and a blob container in it, do the following
170
168
171
169
[Get the connection string to the storage account](../storage/common/storage-configure-connection-string.md).
172
170
173
-
Note the connection string and the container name. You use them in the receive code.
171
+
Note the connection string and the container name. You use them in the code to receive events.
174
172
175
173
---
176
174
177
175
### Install the npm packages to receive events
178
176
179
-
For the receiving side, you need to install two more packages. Inthis quickstart, you use Azure Blob storage to persist checkpoints so that the program doesn't read the events that it has already read. It performs metadata checkpoints on received messages at regular intervals in a blob. This approach makes it easy to continue receiving messages later from where you left off.
177
+
For the receiving side, you need to install two more packages. Inthis quickstart, you use Azure Blob storage to persist checkpoints so that the program doesn't read the events that it already read. It performs metadata checkpoints on received messages at regular intervals in a blob. This approach makes it easy to continue receiving messages later from where you left off.
> For the complete source code, including additional informational comments, go to the [GitHub receiveEventsUsingCheckpointStore.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/eventhubs-checkpointstore-blob/samples/v1/javascript/receiveEventsUsingCheckpointStore.js).
363
361
364
-
You have now received events from your event hub. The receiver program receives events from all the partitions of the default consumer group in the event hub.
362
+
The receiver program receives events from all the partitions of the default consumer group in the event hub.
365
363
366
364
## Clean up resources
367
365
Delete the resource group that has the Event Hubs namespace or delete only the namespace if you want to keep the resource group.
0 commit comments