diff --git a/modules/ROOT/pages/platform/metrics-integration.adoc b/modules/ROOT/pages/platform/metrics-integration.adoc index e4ca114e9..5f2326972 100644 --- a/modules/ROOT/pages/platform/metrics-integration.adoc +++ b/modules/ROOT/pages/platform/metrics-integration.adoc @@ -241,9 +241,9 @@ aura instances get --instance-id | jq '.metrics_integration_u Metrics returned by integration endpoint have the basic granularity reflective of the labels exposed, namely `aggregation`, `instance_id`, `database`. -An Aura instance is typically underpinned by more than one Neo4j DBMS instances to achieve availability and workload scalability. These underlying Neo4j DBMS instances typically get deployed into more than one, user selected, Cloud Provider availability zones in Primary or Secondary modes based on the workload requirements. +An Aura instance is typically underpinned by more than one nodes to achieve availability and workload scalability which typically get deployed into more than one, user selected, Cloud Provider availability zones in Primary or Secondary modes based on the workload requirements. -Metrics Integration now supports a more granular view of the Aura instance metrics with additional data points for availability zone & instance mode combinations. +Metrics Integration supports a more granular view of the Aura instance metrics with additional data points for availability zone & instance mode combinations. This view can be enabled on demand. .Example metric datapoints [source]