Skip to main content
Skip table of contents

Initialize the Event Hubs Beat Using Connection Strings

Before you initialize the Event Hubs 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:

    ./lrctl status

    You should see the open_collector and metrics as shown in the following graphic:

    If the Open Collector is not running correctly, see Troubleshoot the Open Collector in the Open Collector Installation and User Guide.
  2. In the Open Collector, run the following command:

    ./lrctl eventhubbeat start 
  3. When prompted to deploy the Event Hub Beat service on Azure VM, type N.

    Alternatively, to configure the Event Hub Beat using an Azure VM, see Configure the Event Hub Beat Using MSI on Azure VM.

  4. Using the arrow keys, select the cloud service instance type (Public Cloud, China Cloud, or US Gov Cloud).
  5. Enter one or more Event Hub Connection Strings along with a corresponding storage container name, entered one at a time. Note the following:
    1. Event Hub Connection Strings, Storage Connection Strings, and Subscription IDs are stored in an encrypted format in the configuration file.
    2. When you paste a connection string into the command prompt, you may observe it repeated dozens of times. This is cosmetic only. Press Enter to submit the connection string.
    3. If you enter an invalid storage container name, the CLI will prompt again for the valid storage container name.
    4. For commands to inspect or edit configuration, see the configuration information in Open Collector Installation Tips.
  6. Check the status of the service:

    ./lrctl eventhubbeat status

Default Config Values for the Event Hubs Beat

S. No.Field NameDefault Value
4.StorageConnectionStringUser Provided
5.ConnectionStringUser Provided
6.ConsumerGroupUser Provided
7.Time Period5s

Azure Flag

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.