add APM metrics

Author: mdbirnstiehl

solutions/observability/apps/metrics-2.md

@@ -4,11 +4,27 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-metrics.html
 ---
 
-# Metrics
+# Metrics [apm-metrics]
 
-% What needs to be done: Align serverless/stateful
+The **Metrics** overview provides APM agent-specific metrics, which lets you perform more in-depth root cause analysis investigations within the Applications UI.
 
-% Use migrated content from existing pages that map to this page:
+If you’re experiencing a problem with your service, you can use this page to attempt to find the underlying cause. For example, you might be able to correlate a high number of errors with a long transaction duration, high CPU usage, or a memory leak.
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/apm-metrics.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-metrics.md
+:::{image} ../../../images/observability-apm-metrics.png
+:alt: Example view of the Metrics overview in Applications UI in Kibana
+:class: screenshot
+:::
+
+If you’re using the Java APM agent, you can view metrics for each JVM.
+
+:::{image} ../../../images/observability-jvm-metrics-overview.png
+:alt: Example view of the Metrics overview for the Java Agent
+:class: screenshot
+:::
+
+Breaking down metrics by JVM makes it much easier to analyze the provided metrics: CPU usage, memory usage, heap or non-heap memory, thread count, garbage collection rate, and garbage collection time spent per minute.
+
+:::{image} ../../../images/observability-jvm-metrics.png
+:alt: Example view of the Metrics overview for the Java Agent
+:class: screenshot
+:::