Edge Delta AppDynamics Output

Overview

The AppDynamics output will stream analytics and insights to an AppDynamics environment.

Before you can create an output, you must have available the AppDynamics Global account name and an API key. To find your Global Account name, review this document from AppDynamics. To learn how to create new AppDynamics API key, review this document from AppDynamics.

Example

      - name: appdynamics-integration
        type: appdynamics
        host: "<add appdynamics host>"
        global_account_name: "<add global account name>"
        api_key: "<add appdynamics api key>"
        schema_name: "<add-schema-name>"
        features: log,metric,edac
        custom_tags:
          "app": "transaction_manager"
          "region": "us-west-2"

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: appdynamics

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-appdynamics

type: appdynamics

Required

Enter appdynamics.

type: appdynamics

host

Optional

To create a custom installation, enter the name of the AppDynamics host that will receive the data.

host: "<ADD APPDYNAMICS HOST>"

global_account_name

Required

Enter the global account name for your AppDynamics account.

global_account_name: "global123"

api_key

Required

Enter the AppDynamics API key.

api_key: "12345"

schema_name

Required

Enter a name to create a schema that will send data to AppDynamics.

The schema name cannot contain empty spaces.

schema_name: "<ADD-SCHEMA_NAME>"

custom_tags

Optional

This parameter defines key-value pairs that are streamed with every request.

      custom_tags:
        "app": "s_pos_transaction_manager"
        "region": "us-west-2"
        "File Path": "{{.FileGlobPath}}"
        "K8s PodName": "{{.K8sPodName}}"
        "K8s Namespace": "{{.K8sNamespace}}"
        "K8s ControllerKind": "{{.K8sControllerKind}}"
        "K8s ContainerName": "{{.K8sContainerName}}"
        "K8s ContainerImage": "{{.K8sContainerImage}}"
        "K8s ControllerLogicalName": "{{.K8sControllerLogicalName}}"
        "ECSCluster": "{{.ECSCluster}}"
        "ECSContainerName": "{{.ECSContainerName}}"
        "ECSTaskVersion": "{{.ECSTaskVersion}}"
        "ECSTaskFamily": "{{.ECSTaskFamily}}"
        "DockerContainerName": "{{.DockerContainerName}}"
        "ConfigID": "{{.ConfigID}}"
        "Host": "{{.Host}}"
        "Source": "{{.Source}}"
        "SourceType": "{{.SourceType}}"
        "Tag": "{{.Tag}}"

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,log,edac

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.