Skip to content

Add HA monitoring #1196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Apr 15, 2025
Merged

Add HA monitoring #1196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
758f0aa
Added HA metrics part
as51340 Mar 14, 2025
3237f6b
Update monitoring
as51340 Apr 4, 2025
22f13e7
Update HA metrics
as51340 Apr 4, 2025
2f4cdd0
Update pages/clustering/high-availability.mdx
matea16 Apr 14, 2025
387b3a3
Merge branch 'memgraph-3-2' into ha-monitoring
matea16 Apr 14, 2025
7d123be
Merge branch 'memgraph-3-2' into ha-monitoring
matea16 Apr 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion pages/clustering/high-availability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,13 @@ since Raft, as a consensus algorithm, works by forming a majority in the decisio

</Callout>

## Observability

Monitoring the cluster state is very important and tracking various metrics can provide us with a valuable information. Currently, we track
metrics which reveal us p50, p90 and p99 latencies of RPC messages, the duration of recovery process and the time needed to react to changes
in the cluster. We are also counting the number of different RPC messages exchanged and the number of failed requests since this can give
us infomation about parts of the cluster that need further care. You can see the full list of metrics [here](/database-management/monitoring#system-metrics).

<Callout type="info">

When deploying coordinators to servers, you can use the instance of almost any size. Instances of 4GiB or 8GiB will suffice since coordinators'
Expand All @@ -61,7 +68,6 @@ but from the availability perspective, it is better to separate them physically.
</Callout>



## Bolt+routing

Directly connecting to the MAIN instance isn't preferred in the HA cluster since the MAIN instance changes due to various failures. Because of that, users
Expand Down
Loading