Loading

Configure EDOT Cloud Forwarder for Azure

Before deploying EDOT Cloud Forwarder for Azure, configure the Bicep template parameters based on your specific requirements. The template uses the following settings to deploy and configure the EDOT Collector Function App.

The Bicep template is available at the following URL:

The following parameters are available in the Bicep template:

Parameter Description
elasticsearchOtlpEndpoint OTLP service endpoint obtained from Elastic Cloud Serverless or Elastic Cloud Hosted.
elasticsearchApiKey Elasticsearch API key for authentication.
Parameter Default Description Available options
logsDecoder ds Decoder to decode the logs. ds (diagnostic settings)
metricsDecoder ds Decoder to decode the metrics. ds (diagnostic settings) and dcr (Data Collection Rules)
eventHubPartitionCount 4 Number of partitions in the event hubs.
eventHubMessageRetentionInDays 1 Number of days for the event hub data retention.

The Bicep template creates the following resources to process telemetry data:

Resource name Type Description
eventHubNamespace Microsoft.EventHub/namespaces Event Hubs namespace to host the event hubs to stream logs and metrics.
logsEventHub Microsoft.EventHub/namespaces/eventhubs Event hub for the logs.
metricsEventHub Microsoft.EventHub/namespaces/eventhubs Event hub for the metrics.
storageAccount Microsoft.Storage/storageAccounts Storage Account container to store the Event Hubs trigger checkpoint information and the failed messages.
hostingPlan Microsoft.Web/serverfarms Hosting plan that runs the function app.
functionApp Microsoft.Web/sites The function app that runs the EDOT Collector.
applicationInsights Microsoft.Insights/components Application Insights instance to monitor the application.

Note the following:

  • The eventHubNamespace hosts the two event hubs responsible for receiving logs and metrics from Azure services.
  • The storageAccount stores the checkpoint information for the Event Hub triggers, and it also hosts the failed logs and metrics in the logs-error-container and metrics-error-container containers.
  • The functionApp is the core component responsible for running the OTel collector inside the Azure Function.