Quickstart
editQuickstart
edit-
Apply the following specification to deploy Elastic Agent with the System metrics integration to harvest CPU metrics from the Agent Pods. ECK automatically configures the secured connection to an Elasticsearch cluster named
quickstart
, created in the Elasticsearch quickstart.cat <<EOF | kubectl apply -f - apiVersion: agent.k8s.elastic.co/v1alpha1 kind: Agent metadata: name: quickstart spec: version: 8.17.0 elasticsearchRefs: - name: quickstart daemonSet: podTemplate: spec: securityContext: runAsUser: 0 config: inputs: - name: system-1 revision: 1 type: system/metrics use_output: default meta: package: name: system version: 0.9.1 data_stream: namespace: default streams: - id: system/metrics-system.cpu data_stream: dataset: system.cpu type: metrics metricsets: - cpu cpu.metrics: - percentages - normalized_percentages period: 10s EOF
The root user is required to persist state in a
hostPath
volume. See Storing local state in host path volume for options to not run the Agent container as root.Check Configuration examples for more ready-to-use manifests.
-
Monitor the status of Elastic Agent.
kubectl get agent
NAME HEALTH AVAILABLE EXPECTED VERSION AGE quickstart green 3 3 8.17.0 15s
-
List all the Pods that belong to a given Elastic Agent specification.
kubectl get pods --selector='agent.k8s.elastic.co/name=quickstart'
NAME READY STATUS RESTARTS AGE quickstart-agent-6bcxr 1/1 Running 0 68s quickstart-agent-t49fd 1/1 Running 0 68s quickstart-agent-zqp55 1/1 Running 0 68s
-
Access logs for one of the Pods.
kubectl logs -f quickstart-agent-6bcxr
-
Access the CPU metrics ingested by Elastic Agent.
You have two options: