Edge Delta Azure App Insights Output

Stream data to Azure App Insights.

Overview

The Azure AppInsight output will stream analytics and insights to your Azure endpoint.

Example

- name: app-insights
   type: azure
   endpoint: https://dc.services.visualstudio.com/v2/track
   api_key: '{{ Env "TEST_AZURE_APIKEY" }}'

- name: app-insights-with-base-type
   type: azure
   endpoint: https://dc.services.visualstudio.com/v2/track
   api_key: '{{ Env "TEST_AZURE_APIKEY" }}'
   base_type: EventData

Parameters

name

Required

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

name: app-insights

integration_name

Optional

This parameter refers to the organization-level integration created in the Integrations page.

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

integration_name: orgs-azureappinsight

type: azure

Required

Enter azure.

type: azure

api_key

Optional

Enter the AppInsight’s instrumentation key.

api_key: '{{ Env "TEST_AZURE_APIKEY" }}'

endpoint

Optional

Enter the Azure AppInsight endpoint.

endpoint: https://dc.services.visualstudio.com/v2/track

base_type

Optional

This parameter indicates where to funnel data. To funnel data into a tracing index, enter MessageData. To funnel data into an event index, enter EventData.

base_type: EventData

features

Optional

This parameter defines which data types to stream to the destination. If you do not provide a value, then all will be set. To learn more, see the following section on supported feature types.

features: metric

buffer_ttl

Optional

Enter a length of time to retry failed streaming data. After this length of time is reached, the failed streaming data will no longer be tried.

buffer_ttl: 2h

buffer_path

Optional

Enter a folder path to temporarily store failed streaming data. The failed streaming data will be retried until the data reaches its destinations or until the Buffer TTL value is reached. If you enter a path that does not exist, then the agent will create directories, as needed.

buffer_path: /var/log/edgedelta/pushbuffer/

buffer_max_bytesize

Optional

Enter the maximum size of failed streaming data that you want to retry. If the failed streaming data is larger than this size, then the failed streaming data will not be retried.

buffer_max_bytesize: 100MB

Supported Features

See Streaming Features.

Feature Type Supported?
Log Yes
Metrics Yes
Alert as event No
Alert as log No
Health No
Dimensions as attribute Yes
Send as is No
Send as JSON No
Custom tags No
EDAC enrichment No
Message template No
outgoing_bytes.sum Yes
outgoing__raw_bytes.sum Yes
outgoing_lines.count Yes
output buffering to disk No