Skip to main content
Skip table of contents

(LRCloud Only) Initialize the Event Hub Beat through Connection Strings Using Cloud to Cloud Collection

This document explains how to initialize the Event Hub Beat using connection strings using cloud to cloud collection functionality. This is available to LRCloud customers only.


Before you start to initialize the collection from O365, you must ensure the following:

  • Customer is an LRCloud customer that has their environment hosted.
  • Open Collector has been installed in the customer's LRCloud environment on a separate instance. If not, an Open Collector instance must be requested via a support case.
  • Open Collector log source has been accepted and configured for log source virtualization.

Initialize the Beat

  1. Log into the web console as a Restricted Administrator User.
  2. On the top navigation bar, click the Administration icon and select Cloud Log Collection.
  3. At the top of the page, click New Log Source.
  4. Select the tile for Azure Event Hub - Open Collector. 
    The Add Azure Event Hub Log Source screen appears.
  5. Enter the following details:



    NameEnter the name for this log source.
    Description(Optional) Enter a description for this log source.
    Storage Connection String

    Enter the Azure storage account connection string.

    The Storage Account Connection String is in the following format:


    Connection String

    Enter the Event Hub connection string followed by a comma, then followed by the storage container name. A storage container will be created if it is not already configured.

    The Event Hub Connection Strings are in the following format:


  6. Click Save.
  • You can also create multiple configuration for the same log source by creating a new configuration for the same log Source.
  • For security purposes, the values entered are encrypted using LRCrypt.

Default Config Values for EventHubBeat


Field Name

Default Value

4Time Period5s

Azure Flag

JavaScript errors detected

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

If this problem persists, please contact our support.