With Elastic APM, you can capture system and process metrics. These metrics will be sent regularly to the APM Server and from there to Elasticsearch
CPU/Memory metric setedit
This metric set collects various system metrics and metrics of the current process.
if you do not use Linux, you need to install
psutil for this metric set.
The percentage of CPU time in states other than Idle and IOWait, normalized by the number of cores.
The percentage of CPU time spent by the process since the last event. This value is normalized by the number of CPU cores and it ranges from 0 to 100%.
Actual free memory in bytes.
The total virtual memory the process has.
The Resident Set Size. The amount of memory the process occupied in main memory (RAM).
Linux’s cgroup metricsedit
Memory limit for current cgroup slice.
Memory usage in current cgroup slice.
Breakdown metric setedit
Tracking and collection of this metric set can be disabled using the
type: simple timer
This timer tracks the span self-times and is the basis of the transaction breakdown visualization.
sum: The sum of all span self-times in ms since the last report (the delta)
count: The count of all span self-times since the last report (the delta)
You can filter and group by these dimensions:
transaction.name: The name of the transaction
transaction.type: The type of the transaction, for example
span.type: The type of the span, for example
span.subtype: The sub-type of the span, for example
Prometheus metric set (beta)edit
This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
If you use
prometheus_client to collect metrics, the agent can
collect them as well and make them available in Elasticsearch.
The following types of metrics are supported:
- Histograms (requires APM Server / Elasticsearch / Kibana 7.14+)
To use the Prometheus metric set, you have to enable it with the
prometheus_metrics configuration option.
All metrics collected from
prometheus_client are prefixed with
"prometheus.metrics.". This can be changed using the
prometheus_metrics_prefix configuration option.
- The metrics format may change without backwards compatibility in future releases.
Custom metrics allow you to send your own metrics to Elasticsearch.
The most common way to send custom metrics is with the
Prometheus metric set. However, you can also use your
own metric set. If you collect the metrics manually in your code, you can use
from elasticapm.metrics.base_metrics import MetricSet client = elasticapm.Client() metricset = client.metrics.register(MetricSet) for x in range(10): metricset.counter("my_counter").inc()
Alternatively, you can create your own MetricSet class which inherits from the
base class. In this case, you’ll usually want to override the
method, where you can gather and set metrics before they are collected and sent
You can add your
MetricSet class as shown in the example above, or you can
add an import string for your class to the
Your MetricSet might look something like this:
from elasticapm.metrics.base_metrics import MetricSet class MyAwesomeMetricSet(MetricSet): def before_collect(self): self.gauge("my_gauge").set(myapp.some_value)
In the example above, the MetricSet would look up
myapp.some_value and set
my_gauge to that value. This would happen whenever metrics are
collected/sent, which is controlled by the