Get started with default settings using Kubernetes.
4 minute read
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.
Next, you select the environment and in the case of Kubernetes you specify the installation method. In this instance choose Helm.
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.
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.
When your fleet’s agents begin to transmit their health data, click View Pipeline to begin your data pipeline configuration.
The pipeline configuration begins by creating a basic configuration and automatically detecting any sources in the cluster. Click View Sources Found.
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.
Click to turn off Edit Mode. This reveals pipeline statistics per node:
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.
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.
Select the Search tab on the Logs page. You can search for specific logs on this page. See here for more information.
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.
Click the Kubernetes Events tab to view events from Kubernetes.
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.
Click Service Map to view a map of the services within your application architecture and how they interconnect.
Click Pipelines. This page lists your fleets. See here for more information.
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.