Quickstartedit

This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.

  1. 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: 7.12.1
      elasticsearchRefs:
      - name: quickstart
      daemonSet: {}
      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

    See Configuration Examples for more ready-to-use manifests.

  2. Monitor Elastic Agent.

    Retrieve the status of Elastic Agent.

    kubectl get agent
    NAME            HEALTH   AVAILABLE   EXPECTED   VERSION   AGE
    quickstart      green    3           3          7.12.1    15s
  3. List all the Pods belonging 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
  4. Access logs for one of the Pods.

    kubectl logs -f quickstart-agent-6bcxr
  5. Access the CPU metrics ingested by Elastic Agent.

    You have two options:

    • Follow the Elasticsearch deployment guide and run:

      curl -u "elastic:$PASSWORD" -k "https://localhost:9200/metrics-system.cpu-*/_search"
    • Follow the Kibana deployment guide, log in and go to Kibana > Discover.