(LRCloud Only) Initialize the Azure Event Hub Beat Using Cloud-to-Cloud Collection

This document explains how to initialize the Azure Event Hub Beat using the Web Console's cloud-to-cloud functionality. This feature is available only to LRCloud customers.

Prerequisites

Before initializing the Azure Event Hub Beat, do the following:

• Make sure that the customer is an LRCloud customer and has their environment hosted.
• Check if the 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. 
• Ensure that the Open Collector log source has been accepted.
• Check if you have the required strings from Azure.

Apply the Log Source Virtualization Template  

1. Log in to the Client Console in Cameyo.
2. Click Deployment Manager from the toolbar.
3. Click the Log Sources tab.
4. Double-click the required Open Collector Log Source (such as, {instance}-opencollector.c.e3-hub-753dd405.internal Open Collector).
   The Log Message Source Properties window appears.
5. Click the Log Source Virtualization tab. 
6. If not checked, select the Enable Virtualization check box. 
7. Click Create Virtual Log Sources.
   The Create Virtual Log Sources dialog box appears. 
8. In the Virtual Log Sources menu, check the Action check box corresponding to the "Syslog - Open Collector - Azure Event Hub" log source type.
9. Click  Save.
   The Virtual Log Source(s) created prompt appears.
10. Click Ok.
11. Click Apply. 
12. Click Ok.
    The new Log Sources will appear in the grid as children of your parent log source. 
13. Click the System Monitors tab. 
14. Select the Action check box corresponding to the (customerid)-dpawc agent. 
15. Right-click the selection, click Actions and then click Service Restart. 

Initialize the Beat

1. Log in to 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 Cloud Log Collection page, click New Log Source.
   The New cloud log collection dialog box appears.
4. Select the Azure Event Hub - Open Collector tile.
   The Add Azure Event Hub Log Source window appears.
   

   

5. Enter the following details:

   Setting	Description
   Name	Enter 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: DefaultEndpointsProtocol=https;AccountName={StorageAccountName};AccountKey={Key};EndpointSuffix=core.windows.net
   Connection String	Enter the Event Hub connection string followed by a comma, and then 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: Endpoint=sb://{EventHubNamespace}.servicebus.windows.net/;SharedAccessKeyName={PolicyName};SharedAccessKey={Key};EntityPath={EventHub},containername

6. Click Save.
7. Log in to the Client Console in Cameyo.
8. Click Deployment Manager from the toolbar.
9. Click the System Monitors tab. 
10. Select the Action check box corresponding to the dpwac agent.

11. Right-click the selection, click Actions and then click Service Restart.
    

A new log source is created with the provided information based on the virtualized log source that was already created. Collection should start automatically in few minutes.

The Open Collector hosts the log sources. It is recommended to create a new host entity and move the log source to the new host which is done in the log source properties screen and not from the log source grid.

For security, the values entered are encrypted using LRCrypt.

Default Config Values for Azure Event Hub Beat