APM breaking changesedit
This list summarizes the most important breaking changes in APM. For the complete list, go to APM breaking changes.
The following breaking changes are introduced in APM version 8.0.
Indices are now manged by Fleetedit
All index management has been removed from APM Server; Fleet is now entirely responsible for setting up index templates, index lifecycle polices, and index pipelines.
As a part of this change, the following settings have been removed:
-
apm-server.ilm.* -
apm-server.register.ingest.pipeline.* -
setup.*
Data streams by defaultedit
APM Server now only writes to well-defined data streams; writing to classic indices is no longer supported.
As a part of this change, the following settings have been removed:
-
apm-server.data_streams.enabled -
output.elasticsearch.index -
output.elasticsearch.indices -
output.elasticsearch.pipeline -
output.elasticsearch.pipelines
New Elasticsearch outputedit
APM Server has a new Elasticsearch output implementation; it is no longer necessary to manually tune the output of APM Server.
As a part of this change, the following settings have been removed:
-
output.elasticsearch.bulk_max_size -
output.elasticsearch.worker -
queue.*
New source map upload endpointedit
The source map upload endpoint has been removed from APM Server. Source maps should now be uploaded directly to Kibana instead.
Legacy Jaeger endpoints have been removededit
The legacy Jaeger gRPC and HTTP endpoints have been removed from APM Server.
As a part of this change, the following settings have been removed:
-
apm-server.jaeger
Homebrew no longer supportededit
APM Server no longer supports installation via Homebrew.
All removed and changed settingsedit
Below is a list of all removed settings (in alphabetical order) for users upgrading a standalone APM Server to Elastic Stack version 8.0.
apm-server.data_streams.enabled apm-server.ilm.* apm-server.jaeger apm-server.register.ingest.pipeline.* apm-server.sampling.keep_unsampled output.elasticsearch.bulk_max_size output.elasticsearch.index output.elasticsearch.indices output.elasticsearch.pipeline output.elasticsearch.pipelines output.elasticsearch.worker queue.* setup.*
Below is a list of renamed settings (in alphabetical order) for users upgrading a standalone APM Server to Elastic Stack version 8.0.
previous setting --> new setting apm-server.api_key --> apm-server.auth.api_key apm-server.instrumentation --> instrumentation apm-server.rum.allowed_service --> apm-server.auth.anonymous.allow_service apm-server.rum.event_rate --> apm-server.auth.anonymous.rate_limit apm-server.secret_token --> apm-server.auth.secret_token
Supported Elastic Cloud settingsedit
Below is a list of all supported settings (in alphabetical order) for users upgrading an Elastic Cloud standalone cluster to Elastic Stack version 8.0. Any previously supported settings not listed below will be removed when upgrading.
apm-server.agent.config.cache.expiration apm-server.aggregation.transactions.* apm-server.auth.anonymous.allow_agent apm-server.auth.anonymous.allow_service apm-server.auth.anonymous.rate_limit.event_limit apm-server.auth.anonymous.rate_limit.ip_limit apm-server.auth.api_key.enabled apm-server.auth.api_key.limit apm-server.capture_personal_data apm-server.default_service_environment apm-server.max_event_size apm-server.rum.allow_headers apm-server.rum.allow_origins apm-server.rum.enabled apm-server.rum.exclude_from_grouping apm-server.rum.library_pattern apm-server.rum.source_mapping.enabled apm-server.rum.source_mapping.cache.expiration logging.level logging.selectors logging.metrics.enabled logging.metrics.period max_procs output.elasticsearch.flush_bytes output.elasticsearch.flush_interval