[docs][APM] Update APM screenshots (#46235) (#46554)

docs/apm/bottlenecks.asciidoc

@@ -12,7 +12,7 @@ You can think of transactions as the highest level of work you’re measuring wi
 As an example, a transaction could be a request to your server, a batch job, or a custom transaction type.
 * {apm-overview-ref-70}/errors.html[*Errors*] contain information about the original exception that occurred or about a log created when the exception occurred.
 
-Each of these information types have a specific page associated with them in the APM UI.
+Each of these information types have a specific page associated with them in the APM app.
 These various pages display the captured data in curated charts and tables that allow you to easily compare and debug your applications.
 
 For example, you can see information about response times, requests per minute, and status codes per endpoint.

docs/apm/filters.asciidoc

@@ -1,21 +1,29 @@
 [[filters]]
 === Filters
 
-Global filters are ways you can filter your data within the APM UI.
+APM provides two different ways you can filter your data within the APM App:
+
+* <<global-filters>>
+* <<contextual-filters>>
+
+[[global-filters]]
+==== Global filters
+
+Global filters are ways you can filter any and all data across the APM app.
 They are available in the Services, Transactions, Errors, Metrics, and Traces views,
 and any filter applied will persist as you move between pages.
 
 [role="screenshot"]
-image::apm/images/global-filters.png[Global filters available in the APM UI in Kibana]
+image::apm/images/global-filters.png[Global filters available in the APM app in Kibana]
 
 [float]
-==== Global time range
+===== Global time range
 
 The <<set-time-filter,global time range filter>> in {kib} restricts APM data to a specific time period.
 
 [float]
 [[query-bar]]
-==== Query bar
+===== Query bar
 
 The query bar is a powerful data query feature.
 Similar to the query bar in {kibana-ref}/discover.html[Discover],
@@ -27,7 +35,7 @@ See <<query-bar,advanced queries>> for more information and sample queries.
 
 [float]
 [[environment-selector]]
-==== Service environment filter
+===== Service environment filter
 
 The environment selector is a global filter for `service.environment`.
 It allows you to view only relevant data, and is especially useful for separating development from production environments.
@@ -46,3 +54,19 @@ v|*Go:* {apm-go-ref}/configuration.html#config-environment[`ELASTIC_APM_ENVIRONM
 *Ruby:* {apm-ruby-ref}/configuration.html#config-environment[`environment`]
 *Real User Monitoring:* {apm-rum-ref}/configuration.html#environment[`environment`]
 |===
+
+[[contextual-filters]]
+==== Contextual filters
+
+Local filters are ways you can filter your specific APM data on each individual page.
+The filters shown are relevant to your data, and will persist between pages,
+but only where they are applicable -- they are typically most useful in their original context.
+As an example, if you select a host on the Services overview, then select a transaction group,
+the host filter will still be applied.
+
+These filters are very useful for quickly and easily removing noise from your data. 
+With just a click, you can filter your transactions by the transaction result,
+host, container ID, and more. 
+
+[role="screenshot"]
+image::apm/images/local-filter.png[Local filters available in the APM app in Kibana]

docs/apm/getting-started.asciidoc

@@ -15,7 +15,7 @@ To set up the correct index pattern,
 simply click *Load Kibana objects* at the bottom of the Setup Instructions.
 
 After you install an Elastic APM agent library in your application,
-the application automatically appears in the APM UI in {kib}.
+the application automatically appears in the APM app in {kib}.
 No further configuration is required.
 
 [role="screenshot"]

docs/apm/index.asciidoc

@@ -7,7 +7,7 @@
 Elastic Application Performance Monitoring (APM) automatically collects in-depth
 performance metrics and errors from inside your applications.
 
-The **APM** page in {kib} is provided with the basic license. It
+The **APM** app in {kib} is provided with the basic license. It
 enables developers to drill down into the performance data for their applications
 and quickly locate the performance bottlenecks.
 

docs/apm/transactions.asciidoc

@@ -52,6 +52,20 @@ For further details, including troubleshooting and custom implementation instruc
 refer to the documentation for each {apm-agents-ref}[APM Agent] you've implemented.
 ====
 
+[[rum-transaction-overview]]
+==== RUM Transaction overview
+
+The transaction overview page is customized for the JavaScript RUM Agent.
+This page highlights things like *page load times*, *transactions per minute*, and even the *average page load duration distribution by country*.
+
+[role="screenshot"]
+image::apm/images/apm-geo-ui.jpg[average page load duration distribution]
+
+This data is available due to the geo-ip and user agent pipelines being enabled by default,
+which allows for the capture of geo-location and user agent data.
+These visualizations make it easy for you to visualize performance information about your
+end users' experience based on their location.
+
 [[transaction-details]]
 ==== Transaction details