Edge Delta changelog
Edge Delta changelog
edgedelta.com

Updated Workflows

 

New

  

With the recent release of agent version 0.1.20, workflows have been updated.

Specifically, you can use the newly created enabled_hosts parameter to limit the workflow to specific hosts.

With this parameter, the workflow will only run for specified agent hosts. 

Review the following example:

  enabled_hosts_workflow:
    description: "runs only specified hosts"
    input_labels:
      - system
      - docker
      - agent
      - infa-processes
    filters:
      - info
    destinations:
      - '{{ Env "TEST_SUMO" }}'
    enabled_hosts:
      - my.host.us1
      - my.host.us2

To learn more, see Workflows.

Updated Sumo Logic Output

 

New

  

With the recent release of agent version 0.1.20, the Sumo Logic streaming output has been updated. 

Specifically, you can use the newly created send as json parameter to send data in a JSON format, which allows the fields to be auto-parsed and extracted in Sumo.

Review the following example:

    - name: sumo-us-2
      type: sumologic
      endpoint: '{{ Env "EMPTY" "https://endpoint4.collection.us2.sumologic.com/receiver/v1/http/XYZ" }}'
      send_as_json: true

To learn more, see Review Parameters for Stream Outputs and Integrations.

Updated Integration - Loki

 

New

  

In the Edge Delta App, the Loki integration has been updated with a new option.

Specifically, the new Send Alert As Loki Log option allows you to send alerts as a log to a Loki endpoint.

Loki updates.png

To learn more about Loki, see Review Parameters for Stream Outputs and Integrations

Updated Agent Settings - Log

 

New

  

With the recent release of agent version 0.1.18, the Log parameter in the Agent Settings has been updated.

Specifically, you can use the Secure Logging option to hide sensitive data from specified agent logs, such as API keys, secrets, and authentication information. 

Secure Logging.png

To learn more, see Agent Settings.

New Input Type - Google Pub/Sub

 

New

  

With the recent release of agent version 0.1.18, Google Pub/Sub is now a supported input type.

This input type allows you to specify a Pub/Sub project for Edge Delta to monitor. Specifically, EdgeDelta will consume messages from Pub/Sub subscriptions.

In the app, you can use the visual editor or YAML file to add PubSub to an agent configuration.

PubSub.png

To learn more, see Inputs.

New Streaming Destination - ObserveInc

 

New

  

With the recent release of agent version 0.1.18, ObserveInc is now a supported streaming destination.

The ObserveInc output will stream analytics and insights to your ObserveInc endpoint.

In the app, you can use the visual editor or YAML file to add ObserveInc to an agent configuration.

ObserveInc.png

To learn more, see Review Parameters for Stream Outputs and Integrations

Agent Version 0.1.16 

 

New

  

Overview

Version 0.1.16 of the Edge Delta Agent has been released.

While this release contains several enhancements and bug fixes, review the following noteworthy updates:


Graylog Integration

In the Edge Delta App, Graylog is now a supported streaming output.

The Graylog output will stream analytics and insights to your Graylog endpoint. In the app, you can use a YAML file to add Graylog to a configuration.

To add Graylog, access the Integrations page or the Agent Settings page.


AppDynamics Integration

In the Edge Delta App, AppDynamics is now a supported streaming output.

The AppDynamics output will stream analytics and insights to an AppDynamics environment. In the app, you can use the visual editor or YAML file to add AppDynamics to a configuration.

To add AppDynamics, access the Integrations page or the Agent Settings page.


Updates to Datadog Integration

The Datadog Integration has been updated with a new parameter called Send Alert As Datadog Log.

With this update, you can now send alerts as logs.

Datadog Updates.png


Multi-threshold Support

In the Edge Delta App, you can add multi-threshold settings to an agent configuration file.

For example, you can set a threshold to generate an alert when all of the following conditions are met: 

  • anomaly score is > 90
  • response_time_ms.avg is > 250

To set this configuration, use the type parameter, specifically set to AND.

To better understand, review the following sample YAML:

 - name: cluster-errors-multi-threshold 
   type: and 
   interval: 1m 
   conditions: 
   - metric_name: 
http_request_method_updateconfig_latency.avg 
      operator: ">=" 
      value: 100 
    - metric_name: 
http_request_method_deleteconfig_latency.max 
      operator: ">" 
      value: 125 
      consecutive: 5

To update your agent configuration file, visit the Agent Settings page in the Edge Delta App.


Additional Information

For a complete list of updates in this agent release, please visit the Changelog - Agent Releases page.


Notification for Throttling

 

New

  

In the Edge Delta App, a notification has been created to let users know when data ingestion is being throttled.

Specifically, when a data ingestion limit is reached, the Edge Delta agent is throttled, and as a result, a notification will display at the top of the app.

New Throttle Notification.png

To learn more about these limits, please contact Edge Delta Support at support@edgedelta.com.

S3 Integration

 

New

  

In the Edge Delta App, S3 is now a supported streaming output.

The S3 output will stream analytics and insights to an S3 bucket. In the app, you can use a YAML file or visual editor to add S3 to a configuration.

To add S3, access the Integrations page or the Agent Settings page.

OpenMetrics Integration

 

New

  

In the Edge Delta App, OpenMetrics is now a supported streaming output.

The OpenMetrics output will stream analytics and insights to an OpenMetrics endpoint. In the app, you can use a YAML file to add OpenMetrics to a configuration.

To add OpenMetrics, access the Integrations page or the Agent Settings page.