IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Run Elastic Agent on Azure AKS managed by Fleet
editRun Elastic Agent on Azure AKS managed by Fleet
editPlease follow the steps to run the Elastic Agent on Run Elastic Agent on Kubernetes managed by Fleet page.
Important notes:
editOn managed Kubernetes solutions like AKS, Elastic Agent has no access to several data sources. Find below the list of the non available data:
-
Metrics from Kubernetes control plane
components are not available. Consequently metrics are not available for
kube-scheduler
andkube-controller-manager
components. In this regard, the respective dashboards will not be populated with data. - Audit logs are available only on Kubernetes master nodes as well, hence cannot be collected by Elastic Agent.
-
Fields
orchestrator.cluster.name
andorchestrator.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 addorchestrator.cluster.name
andorchestrator.cluster.url
fields for each Kubernetes integration's component:Processors configuration.
- add_fields: target: orchestrator.cluster fields: name: clusterName url: clusterURL