# Install eBPF Agent (Alaz)

To start monitoring your Kubernetes Cluster, you need to create a new Cluster on the Ddosify platform. To achieve this, navigate to the [Clusters page](https://app.ddosify.com/clusters) and click the Add Cluster button. After providing a unique name for the Cluster, you will be navigated to the Observability page, where you will see the [Service Map](https://docs.ddosify.com/ddosify/kubernetes-monitoring/service-map), [Metrics Dashboard](https://docs.ddosify.com/ddosify/kubernetes-monitoring/metrics), and [Distributed Tracing](https://docs.ddosify.com/ddosify/kubernetes-monitoring/distributed-tracing) for this Cluster. 

But before that, you have to install and run our [open-source eBPF agent (Alaz)](https://github.com/ddosify/alaz) as a DaemonSet in your Kubernetes Cluster. Follow the below instructions to set up a new cluster successfully.

{% hint style="info" %}
Installing Alaz on Ddosify Self-Hosted requires some extra steps. For that case, please refer [here](https://app.gitbook.com/o/jN3rtZ38DU58INyTNPm7/s/ugegoRCn84wtxrIelgft/~/changes/115/ddosify/self-hosted/install-ebpf-agent-alaz-on-self-hosted).
{% endhint %}

1. Click the Set Up Cluster button 

   <figure><img src="https://2539979715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FugegoRCn84wtxrIelgft%2Fuploads%2FQVcTkolcpISafnq6OMQ9%2Fimage.png?alt=media&#x26;token=b51b6a13-22e0-4d1e-b632-58fbaa7dcf33" alt=""><figcaption></figcaption></figure>
2. A pop-up will open and show you how to install Alaz via Kubectl or Helm:

   <figure><img src="https://2539979715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FugegoRCn84wtxrIelgft%2Fuploads%2FULu9XkpPCSPPf6M3HyXa%2Fimage.png?alt=media&#x26;token=3a1b0a80-a65d-41dd-97ea-16e34819d990" alt=""><figcaption></figcaption></figure>

#### Kubectl

<figure><img src="https://lh7-us.googleusercontent.com/Nlmc87GCPgmyj28j4_ZW-sROMiev83JqPwmXRfHWZC5Py1iXKQUz5pJUYlppUGeBLiTPxiUESWLx4Dw4_pCo77b7FjmdhqJDm11pZZd6Z_ajm6ZCsKuD1rrUXv2C6oOzyo_K5eDFzIetak3lQTNRS4s" alt="" width="563"><figcaption><p>Kubectl instructions</p></figcaption></figure>

This installs Alaz as a DaemonSet in your cluster. Let's see what each line does:

```
# Deploy Alaz with Kubectl
1. MONITORING_ID=0ce2ef05-ef64-459d-90d9-7f2cbd65fff8
2. curl -sSL https://raw.githubusercontent.com/ddosify/alaz/master/resources/alaz.yaml -o alaz.yaml
3. sed -i"" -e "s/<MONITORING_ID>/$MONITORING_ID/g" alaz.yaml
4. kubectl create namespace ddosify
5. kubectl apply -f alaz.yaml
```

1. Defines the monitoring id of the cluster. It's a unique id for the cluster and is auto-generated by Ddosify.&#x20;
2. Retrieves the Alaz yaml file containing the required declarations. Check [file](https://raw.githubusercontent.com/ddosify/alaz/master/resources/alaz.yaml).
3. Replaces the $MONITORING\_ID variable with the monitoring id declared in Step 1.
4. Creates the `ddosify` namespace.
5. Applies the Alaz yaml file.

#### Helm

<figure><img src="https://lh7-us.googleusercontent.com/yBHo56JR0jOD-7xiziZlNiAei0TJ0bIf3041ASoSPHBgYFTtg_O0KraW4UErLNU2Ffz7EEKYXSDReEG0780ps6YJZ9WimczUSxSkkfuQY00CktVcnlodL13jECPMPi_WuY_hrtecA2JnYxp_mMKsgFE" alt="" width="563"><figcaption><p>Helm instructions</p></figcaption></figure>

This uses the Helm package manager to do the same. It installs Alaz as a DaemonSet in your cluster. Let's see what each line does:

<pre><code><strong># Deploy Alaz with Helm
</strong><strong>1. MONITORING_ID=0ce2ef05-ef64-459d-90d9-7f2cbd65fff8 
</strong>2. helm repo add ddosify https://ddosify.github.io/ddosify-helm-charts/
3. helm repo update
4. kubectl create namespace ddosify
5. helm upgrade --install --namespace ddosify alaz ddosify/alaz --set monitoringID=$MONITORING_ID
</code></pre>

1. Defines the monitoring id of the cluster. It's a unique id for the cluster and is auto-generated by Ddosify.&#x20;

2. Adds the Ddosify Helm chart to your local Helm registry. Check [Helm Chart.](https://github.com/ddosify/ddosify-helm-charts)&#x20;

3. Updates your Helm registry with the addition of Ddosify.

4. Creates the `ddosify` namespace.

5. Installs Alaz in your cluster using Helm by setting the monitoring id. You can also set other parameters like backendHost if you use Self-hosted. Check [Helm Chart parameters](https://github.com/ddosify/ddosify-helm-charts?tab=readme-ov-file#alaz-parameters).&#x20;

6. After a few seconds, [Service Map](https://docs.ddosify.com/ddosify/kubernetes-monitoring/service-map) and [Metrics Dashboard](https://docs.ddosify.com/ddosify/kubernetes-monitoring/metrics) will be ready on Ddosify.

<figure><img src="https://2539979715-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FugegoRCn84wtxrIelgft%2Fuploads%2Fp5wxJHyCJr8sSAsMOknV%2F03_Ddosify_Kubernetes_Service_Map.png?alt=media&#x26;token=c2d4eb2b-24ac-4212-b442-aef1980bb292" alt=""><figcaption><p>Inspect Kubernetes Service Map on Ddosify Platform</p></figcaption></figure>

{% hint style="success" %}
If you require assistance with setting up Alaz, you can join our[ Discord](https://discord.com/invite/9KdnrSUZQg) or send an email to <support@ddosify.com>.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ddosify.com/ddosify/kubernetes-monitoring/install-ebpf-agent-alaz.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.