Quick Start Installation

Overview

This workflow gets you started for POC purposes in a local kubernetes cluster. For more detailed installation instructions for your specific environment, see Edge Delta Fleet Installation.

1. Create a local kubernetes cluster
2. Sign up with Edge Delta
3. Install the Edge Delta Fleet
4. Explore the Edge Delta Interface
5. Edit the Pipeline Configuration

1. Create a Kubernetes Cluster

This workflow uses Docker, minikube and Helm.

First start the Docker daemon then create a kind cluster.

open -a docker

minikube start --driver docker

See Kubernetes Requirements

In this example, a workload is installed in the cluster, as well as Kube State Metrics and Node-Exporter. See Ingest Kubernetes Metrics

2. Sign Up

1. Visit the Edge Delta application web site.
2. Click Sign Up.

3. Enter your account details and click Register. Alternatively, click Sign up with Google.

Your selected password must adhere to the following criteria for validation:

• Includes at least one lower case letter
• Incorporates at least one upper case letter
• Contains at least one digit (0-9)
• Excludes any segment of your username
• Is not a frequently used password
• Is distinct from the last four passwords you have used

Now you are ready to install a fleet of agents.

3. Install an Edge Delta Fleet

1. You can join an existing organization if they allow your email domain. For a quick start in your own test organization, click Create New Organization.

2. Next you create a fleet. Click New Fleet.

3. You can choose either a cloud fleet or edge fleet. For a quick start, choose Edge.

4. Next, you select the environment and in the case of Kubernetes you specify the installation method. In this instance choose Helm.

5. You name your fleet in a way that helps you identify it such as the application name, cluster name and development stage. Then click Generate Deployment Command.

6. A set of commands are generated that are specific to your fleet and deployment method - in this instance Helm. They include the fleet version and the unique Pipeline ID. Run each command in turn.

7. When your fleet’s agents begin to transmit their health data, click View Pipeline to begin your data pipeline configuration.

8. The pipeline configuration begins by creating a basic configuration and automatically detecting any sources in the cluster. Click View Sources Found.

9. You select the sources you are interested in. For a quick start, select All Sources and click Add Sources.

The detected sources are configured in the pipeline and all the required node connections are completed for you. A new fleet with the default configuration is now installed and configured in your cluster.

10. Click to turn off Edit Mode. This will reveal pipeline statistics per node if enough time has passed:

4. Explore the Edge Delta Interface

With a new workload in your cluster your data might be limited as you explore the interface. You can also view the public Play environment, which is connected to Edge Delta managed workloads for demonstration purposes.

1. Click Dashboard and select the K8s Overview dash. It shows an overview of the Kubernetes components that are being monitored by the Fleet. See here for more information.

2. Click the Logs page. It opens on the Search tab. You can search for specific logs on this page. See here for more information.

3. Click the Patterns tab. This page displays detected patterns including those with a negative sentiment. See here for more information.

While the fleet is still new there wont be anomalies yet on the Anomalies tab. Come back in a few hours after a baseline has been established if you want to view anomalies or you can see examples in the Play environment.

4. Click Metrics to view the Metrics Explorer.

5. Click the Inventory tab to view the Metrics Inventory: all the metrics being captured.

6. Click Traces to view request traffic between services.

7. Click Events to view Monitor Events.

8. Click the Kubernetes Events tab to view events from Kubernetes.

9. Click Monitors and select the Manage tab to view the default monitors which generate monitor events from across all fleets and send you alerts about events.

10. Click Service Map to view a map of the services within your application architecture and how they interconnect.

11. Click Pipelines. This page lists your fleets. See here for more information.

12. Click your fleet to view more details.

5. Edit the Pipeline Configuration

Click View/Edit Pipeline to make further changes to your pipeline. Configure a Pipeline contains a how-to on how to update the fleet configuration to cater for your workflow. The Pipeline Components section provides detailed specifications for each node type.