document AZ in AAM and add note about delay to CMI (#459)

Co-authored-by: Jessica Wright <[email protected]>

modules/ROOT/pages/auradb/managing-databases/advanced-metrics.adoc

@@ -87,6 +87,25 @@ The possible aggregations are:
 * *Average* - The average value of the metric across all cluster members.
 * *Sum* - The sum of the metric across all cluster members.
 
+== Detail view
+
+label:AuraDB-Business-Critical[]
+label:AuraDB-Virtual-Dedicated-Cloud[]
+
+An Aura instance can run on multiple servers to achieve availability and workload scalability. 
+These servers are deployed across different Cloud Provider availability zones in the user-selected region. 
+
+Detail view shows distinct data series for availability zone & instance mode combinations. 
+This is presented as an alternative to the aggregations described above. 
+
+Detail view can be enabled with the toggle under the time interval selector.
+
+
+[NOTE]
+====
+Metrics in the Detail view for a new Aura instance may take time to appear because of the way 'availability zone' data is collected.
+====
+
 == Store size metrics
 
 === Resources tab

modules/ROOT/pages/platform/metrics-integration.adoc

@@ -268,6 +268,12 @@ This view can be enabled on demand.
 Contact link:https://support.neo4j.com/[Customer Support] to enable more granular metrics of instances for your tenant.
 ====
 
+[NOTE]
+====
+There may be a delay in more granular metrics being available when a new Aura instance is created. 
+This is because of the way 'availability zone' data is collected.
+====
+
 .Example metric data points
 [source]
 ----
@@ -722,4 +728,3 @@ This also corresponds to the median of the query execution time.
 | Default aggregation
 m| MAX
 |===
-