Breaking Changes

edit

Breaking Changes

edit

APM Server is built on top of libbeat. As such, any breaking change in libbeat is also considered to be a breaking change in APM Server.

7.15

edit

The following breaking changes were introduced in 7.15:

network.connection_type is now network.connection.type 5671
transaction.page and error.page no longer recorded 5872
[preview] This breaking change applies to the experimental tail-based sampling feature. apm-server.sampling.tail now requires apm-server.data_streams.enabled 5952
[beta] This breaking change applies to the beta APM integration. The traces-sampled-* data stream is now traces-apm.sampled-* 5952

7.14

edit

There are no breaking changes in APM Server.

7.13

edit

There are no breaking changes in APM Server.

7.12

edit

There are three breaking changes to be aware of; these changes only impact users ingesting data with Jaeger clients.

Leading 0s are no longer removed from Jaeger client trace/span ids.

This change ensures distributed tracing continues to work across platforms by creating consistent, full trace/span IDs from Jaeger clients, Elastic APM agents, and OpenTelemetry SDKs.
Jaeger spans will now have a type of "app" where they previously were "custom".

If the Jaeger span type is not inferred, it will now be "app". This aligns with the OpenTelemetry Collector exporter and improves the functionality of the time spent by span type charts in the APM app.
Jaeger spans may now have a more accurate outcome of "unknown".

Previously, a "success" outcome was assumed when a span didn’t fail. The new default assigns "unknown", and only sets an outcome of "success" or "failure" when the outcome is explicitly known. This change aligns with Elastic APM agents and the OpenTelemetry Collector exporter.

7.11

edit

There are no breaking changes in APM Server.

7.10

edit

There are no breaking changes in APM Server.

7.9

edit

There are no breaking changes in APM Server.

7.8

edit

There are no breaking changes in APM Server.

7.7

edit

There are no breaking changes in APM Server. However, a previously hardcoded feature is now configurable. Failing to follow these upgrade steps will result in increased span metadata ingestion when upgrading to version 7.7.

7.6

edit

There are no breaking changes in APM Server.

7.5

edit

The following breaking changes have been introduced in 7.5:

Introduced dedicated apm-server.ilm.setup.* flags. This means you can now customize ILM behavior from within the APM Server configuration. As a side effect, setup.template.* settings will be ignored for ILM related templates per event type. See set up ILM for more information.
By default, ILM policies will not longer be versioned. All event types will switch to the new default policy: rollover after 30 days or when reaching a size 50gb. See default policy for more information.
To make use of all the new features introduced in 7.5, you must ensure you are using version 7.5+ of APM Server and version 7.5+ of Kibana.

7.0

edit

The following breaking changes have been introduced in 7.0:

Removed deprecated Intake v1 API endpoints. Upgrade agents to a version that supports APM Server ≥ 6.5. More information.
Moved fields in Elasticsearch to be compliant with the Elastic Common Schema (ECS). More information and changed fields.
Breaking changes in libbeat