IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
APM version 8.15
editAPM version 8.15
editAPM version 8.15.4
editBug fixes
edit- Rollover for all APM data streams is now executing correctly in Elasticsearch 8.15.4, fixing a known issue present in 8.15.0, 8.15.1, 8.15.2 and 8.15.3. The fix is applied through elasticsearch#116219.
APM version 8.15.3
editBug fixes
edit- Fix a panic in OTLP label setting when receiving on non-compliant attribute array values 13950
Added
edit-
Map OpenTelemetry instrumentation scope to
Service.Framework.*
for all signal types. 13903
APM version 8.15.2
editBug fixes
edit- Fix broken APM Agents configuration cache when there are more than 100 agent config entries 13958
APM version 8.15.1
editBug fixes
edit- Fix fallback memory limit check conversion from Bytes to Gigabytes 13838
- Fix Elasticsearch apm-data plugin to fallback to ILM policy for data streams using default APM integration and not explicitly migrated to data stream lifecycle. More details are available in the APM known issues page 13918
-
Remove from logs the error reason returned by Elasticsearch for
x_content_parse_exception
error 13853 -
Fix ingestion failure when
ip
resource attribute has value0.0.0.0
in OpenTelemetry events from Jaeger 13852 - Fix possible nil pointer dereference when parsing stacktraces in OpenTelemetry events 13852
- Fix missing tracking in instrumentation metrics for certain request-level status codes from Elasticsearch bulk responses 13853
Added
edit- Support OpenTelemetry Java agent inferred span links 13852
APM version 8.15.0
editBug fixes
edit-
Avoid data race due to reuse of
bytes.Buffer
in ES bulk requests 13155 -
APM Server now relies on the Elasticsearch apm-data plugin’s index templates, which reverts some unsafe uses of
flattened
field types 12066 -
Add
error.id
to jaeger errors 13196 -
Process
host.ip
resource attribute for OTel 13614 - Fix a bug where indexed OpenTelemetry events and their aggregated metrics may contain incorrect label values from other events when the affected OpenTelemetry event has resource attribute values that are slices. This bug may also cause a panic with a message like "panic: runtime error: slice bounds out of range [-4:]" from apm-aggregation library. 13822
Breaking Changes
edit-
Integration custom ingest pipelines
logs-apm.integration@custom
,metrics-apm.integration@custom
, andtraces-apm.integration@custom
are no longer supported. Any existing pipelines above will need to be moved to the more fine-grained\*-apm*@custom
ingest pipelines 12066
Added
edit-
Add
elasticsearch.flushed.uncompressed.bytes
metric 13155 - APM Server now relies on the Elasticsearch apm-data plugin’s index templates, removing the requirement to install the APM integration package 12066
- Upgraded bundled APM Java agent attacher CLI to version 1.50.0 13326
- Enable Kibana curated UIs to work with hostmetrics from OpenTelemetry’s hostmetricsreceiver 13196
- Add require data stream to bulk index requests 13398
- Support self-instrumentation when in managed mode by getting tracing configs via reloader 13514 13653 13691 13790
-
Add mapping for OpenTelemetry attribute
messaging.destination.name
to deriveservice.target
correctly 13472 -
APM Server now automatically retries document-level 429s from Elasticsearch to avoid dropping data.
output.elasticsearch.max_retries
now controls both request-level and document-level retries, and defaults to3
. 13620