diff --git a/docs/breaking-changes.asciidoc b/docs/breaking-changes.asciidoc index 4e27adae14a..1c55101bc86 100644 --- a/docs/breaking-changes.asciidoc +++ b/docs/breaking-changes.asciidoc @@ -4,7 +4,18 @@ APM Server is built on top of {beats-ref}/index.html[libbeat]. As such, any breaking change in libbeat is also considered to be a breaking change in APM Server. [float] -==== HEAD +==== 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 {apm-server-ref}/ilm.html#ilm-setup[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 {apm-server-ref}/ilm.html#ilm-default[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. [float] ==== 7.0 diff --git a/docs/guide/apm-breaking-changes.asciidoc b/docs/guide/apm-breaking-changes.asciidoc index 8e3c39332e6..6606e4070cb 100644 --- a/docs/guide/apm-breaking-changes.asciidoc +++ b/docs/guide/apm-breaking-changes.asciidoc @@ -3,6 +3,7 @@ This section discusses the changes that you need to be aware of when migrating your application from one version of APM to another. +* <> * <> * <> * <> @@ -22,6 +23,29 @@ Also see <>. // end::notable-v8-breaking-changes[] +[[breaking-7.5.0]] +=== 7.5.0 APM Breaking changes + +// tag::notable-v75-breaking-changes[] + +APM Server:: ++ +* 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 {apm-server-ref}/ilm.html#ilm-setup[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 {apm-server-ref}/ilm.html#ilm-default[default policy] for more information. + +APM:: ++ +* 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. + +// tag::notable-v75-breaking-changes[] + [[breaking-7.4.0]] === 7.4.0 APM Breaking changes diff --git a/docs/guide/apm-release-notes.asciidoc b/docs/guide/apm-release-notes.asciidoc index 66f2b386417..f3e6b5bb2d5 100644 --- a/docs/guide/apm-release-notes.asciidoc +++ b/docs/guide/apm-release-notes.asciidoc @@ -7,6 +7,7 @@ For a full list of changes, see the {apm-server-ref-v}/release-notes.html[APM Server Release Notes] or the {kibana-ref}/release-notes.html[Kibana Release Notes]. +* <> * <> * <> * <> @@ -25,6 +26,46 @@ For a full list of changes, see the // end::notable-v8-highlights[] +[[release-highlights-7.5.0]] +=== APM version 7.5.0 + +// tag::notable-v75-highlights[] + +IMPORTANT: 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. + +*APM app in Kibana* + +* {kibana-ref}/transactions.html[Aggregate Service Breakdown Charts] is GA. +Visualize where your applications and services are spending most of their +time, and find the root cause of a performance problem quickly. +Not yet available for the .NET Agent. + +[role="screenshot"] +image::images/breakdown-release-notes.png[Aggregate Service Breakdown Charts] + +* {kibana-ref}/agent-configuration.html[APM Agent remote configuration] is GA. +View and edit certain configurations directly in Kibana without having to restart your Agents. +In 7.5, we're introducing two additional configurations: +** `CAPTURE_BODY` - Optionally capture the request body of an HTTP transaction. +** `TRANSACTION_MAX_SPANS` - Limit the number of spans recorded per transaction. + +In addition, Agent remote configuration now supports all services and environments. +This means you can configure multiple services and environments in just one setting. + +[role="screenshot"] +image::images/remote-config-release-notes.png[APM Agent configuration] + +* {apm-java-ref}/metrics.html[JVM instance level visibility]: +It's easier than ever to troubleshoot your individual JVM instances. +Select a JVM to see individual CPU usage, memory usage, heap or non-heap memory, +thread count, garbage collection rate, and garbage collection time spent per minute. + +[role="screenshot"] +image::images/jvm-release-notes.png[JVM instance level visibility] + +// end::notable-v75-highlights[] + [[release-highlights-7.4.0]] === APM version 7.4.0 diff --git a/docs/guide/images/breakdown-release-notes.png b/docs/guide/images/breakdown-release-notes.png new file mode 100644 index 00000000000..afca76a7632 Binary files /dev/null and b/docs/guide/images/breakdown-release-notes.png differ diff --git a/docs/guide/images/jvm-release-notes.png b/docs/guide/images/jvm-release-notes.png new file mode 100644 index 00000000000..ffeab27e102 Binary files /dev/null and b/docs/guide/images/jvm-release-notes.png differ diff --git a/docs/guide/images/remote-config-release-notes.png b/docs/guide/images/remote-config-release-notes.png new file mode 100644 index 00000000000..19e52a203be Binary files /dev/null and b/docs/guide/images/remote-config-release-notes.png differ