A newer version is available. For the latest information, see the
current release documentation.
APM version 7.16
editAPM version 7.16
editAPM Server version 7.16.3
editNo significant changes.
APM Server version 7.16.2
editNo significant changes.
APM version 7.16.1
editBug fixes
editAPM version 7.16.0
editBreaking Changes
edit- Removed unused stacktrace/frame monitoring counters 5984
- Removed unused support for top-level metricsets and metricset tags for RUMv3 6065
-
Removed
apm-server.mode
configuration, and "experimental" fields 6086 -
transaction.sampled
is now only set for sampled transactions 6066 -
Unknown metrics are dropped when
transaction.*
orspan.*
are present in a metricset 6111 -
Removed
metricset.period
from service_destination metrics 6111 -
Removed
http.request.socket
fields 6152 -
Removed unused
transaction.duration.{count,sum.us}
metric fields 6180 -
Removed
ProcessPending
self-instrumentation events 6243 - Removed warm phase from default ILM policy 6322
-
Removed unused
transaction.breakdown.count
metric field 6366 -
[preview]
This breaking change applies to the experimental tail-based sampling feature.
Changed
apm-server.sampling.tail.events.*
metrics semantics 6273 -
[preview]
This breaking change applies to the experimental tail-based sampling feature.
Removed
apm-server.sampling.tail.storage_dir
config 6236
Bug fixes
edit- Use timestamp of original events for transaction/span metrics 6311
-
Populate the timestamp field for
agent_config
metricsets 6382 -
Query elasticsearch output
cluster_uuid
on startup 6591 - Skip unhandled fields in bulk responses in the experimental Elasticsearch output 6631
-
Fix the format of
@timestamp
to include fractional seconds when using experimental Elasticsearch output 6646 - NaN and +/-Inf values are now filtered out when translating OTLP metrics 6698
Intake API changes
editAdded
edit-
The
error.log.message
orerror.exception.message
field of errors will be copied to the ECS fieldmessage
5974 - Add histogram dynamic_template to app metrics data stream 6043
-
With
apm-server.data_streams.enabled
in standalone mode, the server now accepts and enqueues events while waiting for the integration to be installed 6130 - We now collect span destination metrics for transactions with too many spans (for example due to transaction_max_spans or exit_span_min_duration) when collected and sent by APM agents 6200
- Define index sorting for internal metrics data stream 6116
- Index OpenTelemetry span events and Jaeger logs into a log data stream 6122
- HTTP server errors (e.g. TLS handshake errors) are now logged 6141
-
Span documents now duplicate extended HTTP fields, which were previously only under
span.http.*
, underhttp.*
6147 -
We now record the direct network peer for incoming requests as
source.ip
andsource.port
; origin IP is recorded inclient.ip
6152 - Add an experimental endpoint for AWS Kinesis Data Firehose 6299
-
output.elasticsearch.experimental
can be used to enable a new, experimental Elasticsearch output using the go-elasticsearch client 5970 - Added support for gzip compression to the experimental Elasticsearch output 6449
-
When
auth.anonymous.enabled
isn’t specified and RUM is enabled (rum.enabled:true
),auth.anonymous.enabled
will be set totrue
6607 -
Transaction metrics now also group by
service.node.name
,cloud.provider
,cloud.region
,cloud.availability_zone
6323
Deprecated
edit-
Setting
service.version
as a span tag (Jaeger) or attribute (OTel) is deprecated; use tracer tags (Jaeger) and resource attributes (OTel) 6131 - Setting up Elasticsearch templates, ILM policies, and pipelines directly with apm-server is now deprecated. Users should use the integration package 6145
-
span.http.*
fields are deprecated, replaced byhttp.*
, and will be removed in 8.0 6147 -
Add deprecation warning for
sampling.keep_unsampled=true
6285 -
processors.*
config, which was never officially supported in apm-server, is now explicitly deprecated and will be removed in 8.0 6367 - Support for uploading source maps to APM Server is deprecated, and will be removed in 8.0. Users should use the new Kibana REST API in conjunction with the integration package 6432