Loading

EDOT Cloud Forwarder for Azure

EDOT Cloud Forwarder (CF) for Azure allows you to stream telemetry data from Azure services to an Elasticsearch cluster. EDOT CF for Azure supports the following sources:

Source Description
Activity log Logs generated by Azure Monitor.
Note

We are working to support other sources. Get in touch to let us know of any specific requirements that might influence our plans.

To collect telemetry data using EDOT Cloud Forwarder for Azure, you need:

  • An Azure subscription
  • Azure CLI
  • Bicep extension for Azure CLI
  • An Elastic Managed OTLP endpoint and an API key
Important

EDOT Cloud Forwarder for Azure requires a Managed OTLP endpoint and an API key. Managed OTLP is available for Elastic Cloud Serverless and will soon be available for Elastic Cloud Hosted.

For self-managed deployments, set up an EDOT Collector in Gateway mode that ingests OTel data from the edge setup into the self-managed Elastic Stack.

To retrieve your Elastic Cloud Managed OTLP Endpoint endpoint address and API key, follow these steps:

  1. In Elastic Cloud, create an Observability project or open an existing one.
  2. Go to Add data, select Applications and then select OpenTelemetry.
  3. Copy the endpoint and authentication headers values.

Alternatively, you can retrieve the endpoint from the Manage project page and create an API key manually from the API keys page.

  1. Log in to the Elastic Cloud Console.
  2. Find your deployment on the home page or on the Hosted deployments page, and then select Manage.
  3. In the Application endpoints, cluster and component IDs section, select Managed OTLP.
  4. Copy the public endpoint value.
Important

Trim the API key from Authorization=ApiKey MYKEYVALUE... to just MYKEYVALUE... before using it as the argument to the elasticApiKey parameter.

To use EDOT Cloud Forwarder for Azure, you need an Azure subscription with permissions to create resources.

The Bicep template for EDOT Cloud Forwarder creates the following resources:

  • Function App
  • App Service plan
  • Event Hubs Namespace with two Event Hubs (logs and metrics)
  • Storage account
  • Application Insights workspace

You can use the Azure CLI to deploy and manage resources required for EDOT Cloud Forwarder.

To install Azure CLI, refer to the official documentation.

EDOT Cloud Forwarder for Azure uses Bicep to define all the necessary resources and their dependencies.

After you've installed Azure CLI, install Bicep by running the following command:

az bicep install

Before deploying EDOT Cloud Forwarder for Azure, take the following into consideration:

  • The logs event hub supports Azure resource logs.
  • Support for additional encoding extensions for logs and metrics will be added in future releases.