Install on Kubernetes

Deploy the Sensobit agent as a DaemonSet so every node reports to ingest.sensobit.com.

Run one agent pod per node. The agent reads the node filesystem, kubelet cgroup data, and the container runtime socket.

Helm

helm repo add sensobit https://charts.sensobit.com
helm repo update
helm install sensobit-agent sensobit/agent \
  --namespace sensobit \
  --create-namespace \
  --set apiKey=YOUR_API_KEY \
  --set ingestion.url=https://ingest.sensobit.com \
  --set agent.namespace=production

DaemonSet

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: sensobit-agent
  namespace: sensobit
spec:
  selector:
    matchLabels:
      app: sensobit-agent
  template:
    metadata:
      labels:
        app: sensobit-agent
    spec:
      hostNetwork: true
      hostPID: true
      containers:
        - name: agent
          image: sensobit/agent:latest
          env:
            - name: SENSOBIT_API_KEY
              valueFrom:
                secretKeyRef:
                  name: sensobit-agent
                  key: api-key
            - name: INGESTION_URL
              value: https://ingest.sensobit.com
            - name: HOSTNAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            - name: SENSOBIT_NAMESPACE
              value: production
          volumeMounts:
            - name: proc
              mountPath: /host/proc
              readOnly: true
            - name: sys
              mountPath: /host/sys
              readOnly: true
            - name: docker-sock
              mountPath: /var/run/docker.sock
              readOnly: true
            - name: varlog
              mountPath: /var/log
              readOnly: true
      volumes:
        - name: proc
          hostPath:
            path: /proc
        - name: sys
          hostPath:
            path: /sys
        - name: docker-sock
          hostPath:
            path: /var/run/docker.sock
        - name: varlog
          hostPath:
            path: /var/log

Create the secret first:

kubectl create namespace sensobit
kubectl create secret generic sensobit-agent \
  --namespace sensobit \
  --from-literal=api-key=YOUR_API_KEY
kubectl apply -f sensobit-agent-daemonset.yaml
kubectl -n sensobit logs -l app=sensobit-agent -f

If the cluster uses containerd instead of Docker, mount the containerd socket your runtime exposes and keep hostPID / hostNetwork enabled so process and network collectors see node-level data.

What you see in the console

Each node appears as a host. Container metrics include pod workloads on that node. Use host tags such as cluster and nodepool in the Helm values or DaemonSet env to filter dashboards.

Optional cluster OTLP

To send application traces from the cluster, either:

Enable the agent's local OTLP receiver and point SDKs at the node IP on port 4318, or
Send OTLP HTTP directly to https://ingest.sensobit.com/v1/traces as described in OTLP traces.

Helm

DaemonSet

What you see in the console

Optional cluster OTLP

On this page