Edge Delta Fleet Installation

Overview

Edge Delta Fleets are installed in your environment as close as possible to your data sources. Each Fleet receives its Pipeline configuration from the Edge Delta processing engine (Edge Delta back end).

A single Fleet can consist of agents in multiple different environments, all configured with the same Pipeline.

See here for more details about the architecture.

Configuration Architecture

Each Fleet is configured with a Pipeline using Visual Pipelines or a yaml file. A unique Pipeline ID is used by each Fleet to communicate with the Edge Delta web app to populate your dashboard and retrieve its configuration.

Installation Overview

There are two key components that are used during the Edge Delta Fleet installation:

1. The Pipeline. The Edge Delta web app generates a default Pipeline that you can use without further configuration. A Fleet configured with the default Pipeline sends basic data about your environment to your Edge Delta web app, which can also be used to manage and test the Pipeline. Any configuration changes that you make in the app, such as integrating data sources and destinations, are automatically pushed to the Fleets with matching Pipeline IDs.
2. The Pipeline ID. Each Fleet is associated with a Pipeline ID. This key is used when you install the Fleet to identify the Pipeline it should use and to authenticate its connection to your Edge Delta back end.

To install the Fleet, you deploy it in your environment and pass in the Pipeline ID as the secret API key.

Installation Environments

The following deployment options are available:

• Kubernetes
• Linux
• Windows
• macOS
• Amazon ECS
• Docker

In addition, Edge Delta offers Cloud Fleets.

Related Content