Skip to main content
Skip table of contents

Initialize the Event Hub Beat using MSI

Before you initialize the Beat, you must have the Open Collector installed. If you do not already have it installed, follow the instructions in the Open Collector Installation and User Guide, and then return to this topic.

  1. To confirm the Open Collector is running, run the following command:

    CODE
    ./lrctl status

    You should see the open_collector and metrics listed:

  2. In the Open Collector, run the following command:

    CODE
    ./lrctl eventhubbeat start
  3. At the prompt to deploy the Event Hub Beat service on Azure VM, type Y

    If you do not want to deploy the Event Hub Beat service on Azure VM, follow the steps in Initialize the Event Hubs Beat Using Connection Strings.

  4. Enter the following information:

    1. Enter the Subscription ID.

      Event Hub Connection Strings, Storage Connection Strings, and Subscription IDs are stored in encrypted format in the configuration file

    2. Enter the Resource Group Name.
    3. Enter the Storage Name.
    4. Enter Event Hub Namespace Name.
    5. Enter Event Hub Instance Name.
    6. Enter Storage Container Name.

      You can enter more than one event hub namespace, event hub instance name, and storage container name at a time.
  5. When you are finished, type C.
    The configuration saves and service starts successfully.
                                                                                                                                                                                                                                                                                                                                                                                                                            
  6. To check the status of the service, run the following command:

    CODE
    ./lrctl eventhubbeat status

Default Config Values for EventHubBeat:

S. No.

Field Name

Default Value

1.period1s
2.HeartbeatInterval5m0s 
3.HeartbeatDisabledfalse
4.StorageConnectionStringUser Provided

5.

ConnectionStringUser Provided
6.ConsumerGroupUser Provided
7.Time Period5s
8.Azure Flagfalse
9.SubscriptionIDUser Provided
10.ResourceGroupNameUser Provided
11.EventHubDetailsUser Provided
12.StorageAccountNameMSIUser Provided
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.