Default Edge Delta Configuration
Edge Delta deploys with a default pipeline.
3 minute read
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.
This workflow uses Docker, minikube and Helm.
First start the Docker daemon then create a kind cluster.
open -a docker
minikube start --driver docker
Your selected password must adhere to the following criteria for validation:
Now you are ready to install a fleet of agents.
prod_eks
.A new fleet with the default configuration is now installed in your cluster.
Note: there are no application workloads generating logs in your cluster so your dashboards may be sparsely populated for now.
Install a workload in your cluster to view the web app in action. Alternatively, see the public Play environment, which is connected to Edge Delta managed workloads for demonstration purposes.
You need at least one workload in your cluster for data to populate the Kubernetes Dashboard.
Click Logs and select the Patterns tab. This page displays detected patterns including those with a negative sentiment. 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 Metrics and use the Metrics Explorer or view the Metrics Inventory to see all the metrics being captured.
Explore Events, Traces and the Service Map.
Click Monitors and select the Manage tab to view the default monitors which send you alerts about events from across all fleets.
Click Pipelines. This page lists your fleets and you can edit their pipelines using the GUI. See here for more information.
Configure a Pipeline contains a how-to on how to update the fleet configuration to cater for your workflow. The Pipeline Configuration section provides detailed specifications for each node type.
Edge Delta deploys with a default pipeline.