[Elastic APM](https://www.elastic.co/guide/en/apm/get-started/current/overview.html) is an application performance monitoring system built on the Elastic Stack. This chart is to install the server part of the system. See the official documentation to setup the agent part of the system. Even though apm-server is built by the Elastic team, it supports alternative outputs other than Elasticsearch via built-in beat output plugins and community plugins. For example, [awsbeats](https://github.com/s12v/awsbeats) enables apm-server to write collected application traces to AWS Kinesis Streams. Other changelog: - Include the commented-out elasticsearch output too support common use-cases - Include the configuraion table in the README
apm-server
apm-server is the server receives data from the Elastic APM agents and stores the data into a datastore like Elasticsearch.
Introduction
This chart deploys apm-server agents to all the nodes in your cluster via a DaemonSet.
By default this chart only ships a single output to a file on the local system. Users should set config.output.file.enabled=false and configure their own outputs as documented
Prerequisites
- Kubernetes 1.9+
Installing the Chart
To install the chart with the release name my-release, run:
$ helm install --name my-release stable/apm-server
After a few minutes, you should see service statuses being written to the configured output, which is a log file inside the apm-server container.
Tip
: List all releases using
helm list
Uninstalling the Chart
To uninstall/delete the my-release deployment:
$ helm delete my-release
The command removes all the Kubernetes components associated with the chart and deletes the release.
Configuration
The following table lists the configurable parameters of the apm-server chart and their default values.
| Parameter | Description | Default |
|---|---|---|
image.repository |
The image repository to pull from | docker.elastic.co/apm/apm-server |
image.tag |
The image tag to pull | 6.2.4 |
image.pullPolicy |
Image pull policy | IfNotPresent |
rbac.create |
If true, create & use RBAC resources | true |
rbac.serviceAccount |
existing ServiceAccount to use (ignored if rbac.create=true) | default |
config |
The content of the configuration file consumed by apm-server. See the apm-server documentation for full details | |
plugins |
List of beat plugins | |
extraVars |
A map of additional environment variables | |
extraVolumes, extraVolumeMounts |
Additional volumes and mounts, for example to provide other configuration files | |
resources.requests.cpu |
CPU resource requests | |
resources.limits.cpu |
CPU resource limits | |
resources.requests.memory |
Memory resource requests | |
resources.limits.memory |
Memory resource limits |
Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,
$ helm install --name my-release \
--set rbac.create=true \
stable/apm-server
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml stable/apm-server
Tip
: You can use the default values.yaml