Edge Delta Config Packs

Import a config pack into an existing agent configuration.

  3 minute read  

Configuration v2

Overview

You can import a predefined config pack for an existing agent configuration. It includes pre-populated infrastructure and cloud service definitions directly into an agent configuration.

To import a config pack, you must:

  • Create an input or reference an existing input
  • Create an agent configuration
  • Add the config pack’s import statement into the new agent configuration

AWS Application Load Balancer (ALB) config pack

Currently, Edge Delta provides an AWS Application Load Balancer (ALB) config pack

Based on market popularity and customer feedback, Edge Delta will regularly publish new config packs with different functionalities.

This config pack will monitor the following data types:

  • Status code distributions
  • Response times
  • Top URIs that return 4xx and 5xx

As raw data flows through the data pipeline, this config pack will:

  • Automatically populate underlying configurations to extract and monitor data types
  • Route basic insights to a configured streaming destination

Import the AWS Application Load Balance (ALB) Config Pack

Step 1: Create an S3 Input

You must create an S3 SQS input to publish S3 events to AWS SQS. This input should sync with your AWS ALB access logs output.

To learn how to enable access logs for your load balancer, review this document from Amazon.

Step 2: Obtain Input and Integration Information

When you import the config pack into an agent configuration, you will need to update the config pack with the following information about the S3 SQS input:

  • labels (name of the input)
  • sqs_url
  • access_key_id
  • access_secret
  • region
  • The name of the integration / output to stream the analytical data

You get this information from the agent configuration in the inputs section.

To obtain the name of the integration:

Click Admin - Integrations. Select the integration from the list of Existing Integrations,

(Optional) Step 3: Access AWS to Update Notification Preferences

When you stream AWS ALB access logs to a specified S3 bucket, the access logs files will be published to the S3 bucket every 5 minutes.

However, as an optional step, you can update your S3 bucket to send a notification for every new log file to the configured Amazon Simple Queue Service (SQS).

To learn how to configure your S3 bucket to send notifications to the Amazon SQS queue, please review this document from Amazon.

Step 4: Create and Import an Agent Configuration

  1. Click Pipelines - Agent Settings.
  2. Click Create Configuration.
  3. Select Kubernetes and enter a name.
  4. Paste the following text into the YAML file but replace the imports, inputs and outputs details with your own then click Save.:
version: v2
agent_settings:
  tag: aws-alb-test
  
imports:
  - name: "aws-lb"
    pack_id: "edgedelta/aws-lb:v0"
    params:
      InputLabel: "aws-lb-access-log"
      IntegrationName: "sumo-us-2"

inputs:
  s3_sqs:
    - labels: "aws-lb-access-log"
      sqs_url: "https://sqs.us-west-2.amazonaws.com/XXXXXXXX/SQS_NAME"
      access_key_id: "ACCESS_KEY_ID"
      access_secret: "ACCESS_SECRET_KEY"
      region: "us-west-2"
      log_type: alb

outputs:
  streams:
    - name: "sumo-us-2"
      type: "sumologic"
      endpoint: "SUMOLOGIC_ENDPOINT"
      features: "metric, edac, topk, cluster"