Merge pull request #4052 from dedemorton/backport/7.9/pr-4042

[7.9][docs] Add 7.9 release highlights (#4042)

Author: dedemorton

changelogs/7.9.asciidoc

@@ -19,7 +19,7 @@ https://github.com/elastic/apm-server/compare/v7.8.0\...v7.9.0[View commits]
 [float]
 ==== Added
 * Support configurable response headers for the RUM endpoints {pull}3820[3820]
-* Support custom ILM index suffix {pull}3826[3826],{pull}3905[3905]
+* Support custom ILM index suffix {pull}3826[3826], {pull}3905[3905]
 * Jaeger traceIds/spanIds are formatted without leading zeros {pull}3849[3849]
 * Index Page URL and referer as ECS fields {pull}3857[3857]
 * Map the Jaeger attribute message_bus.destination to the Elastic APM type messaging {pull}3884[3884]

docs/guide/apm-release-notes.asciidoc

@@ -34,7 +34,32 @@ For a full list of changes, see the
 === APM version 7.9.0
 
 // tag::notable-v79-highlights[]
-// Coming soon...
+OpenTelemetry integration::
+
+Elastic’s OpenTelemetry integration allows you to reuse your existing OpenTelemetry instrumentation to quickly analyze distributed traces and metrics with the Elastic Stack.
++
+Elastic’s integration is designed to drop right into your current OpenTelemetry setup. We’ve done this by extending the "contrib" OpenTelemetry collector and adding an Elastic exporter. This exporter translates the OpenTelemetry trace data collected from your services to Elastic’s protocol, before sending the data to the Elastic Stack. By extending the OpenTelemetry collector, no changes are needed in your instrumented services in order to begin using the Elastic Stack.
++
+[role="screenshot"]
+image::images/open-telemetry-elastic-arch.png[OpenTelemetry Elastic architecture diagram]
++
+See {apm-overview-ref-v}/open-telemetry-elastic.html[OpenTelemetry integration]
+for more information.
+
+Machine learning integration improvements::
+
+The Machine learning integration initiates a new job predefined to calculate anomaly scores on APM transaction durations.
+With this integration, you can quickly pinpoint anomalous transactions and see the health of
+any upstream and downstream services.
++
+In previous releases, machine learning jobs were initiated at the service level.
+In 7.9, we've moved jobs to the environment level—this means any new services added to your architecture will automatically be able to take advantage of preexisting machine learning jobs without any additional configuration.
++
+[role="screenshot"]
+image::images/7.8-service-map-anomaly.png[APM Service maps]
++
+See {kibana-ref}/machine-learning-integration.html[machine learning integration] for more information.
+
 // end::notable-v79-highlights[]
 
 [[release-highlights-7.8.0]]

docs/guide/opentelemetry-elastic.asciidoc

@@ -34,6 +34,7 @@ before sending the data to the Elastic Stack.
 By extending the OpenTelemetry collector,
 no changes are needed in your instrumented services in order to begin using the Elastic Stack.
 
+[role="screenshot"]
 image::images/open-telemetry-elastic-arch.png[OpenTelemetry Elastic architecture diagram]
 
 [float]