Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Alexander Bouriakov <[email protected]>
  • Loading branch information
ravikiran-sulikeri and alexnb authored Aug 29, 2024
1 parent 3a0d9c9 commit c337cb7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions modules/ROOT/pages/platform/metrics-integration.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -241,9 +241,9 @@ aura instances get --instance-id <YOUR_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]
Expand Down

0 comments on commit c337cb7

Please sign in to comment.