Type to search.

Run Elastic Agent on Azure AKS managed by Fleet

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Follow the steps to run the Elastic Agent on Run Elastic Agent on Kubernetes managed by Fleet page.

Important notes:

On managed Kubernetes solutions like AKS, Elastic Agent has no access to several data sources. Find below the list of the non available data:

  1. Metrics from Kubernetes control plane components are not available. Consequently metrics are not available for kube-scheduler and kube-controller-manager components. In this regard, the respective dashboards will not be populated with data.

  2. Audit logs are available only on Kubernetes master nodes as well, hence cannot be collected by Elastic Agent.

  3. Fields orchestrator.cluster.name and orchestrator.cluster.url are not populated. orchestrator.cluster.name field is used as a cluster selector for default Kubernetes dashboards, shipped with Kubernetes integration.

    In this regard, you can use add_fields processor to add orchestrator.cluster.name and orchestrator.cluster.url fields for each Kubernetes integration's component:

    YAML 
    - add_fields:
    target: orchestrator.cluster
    fields:
      name: clusterName
      url: clusterURL