Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
21 changes: 21 additions & 0 deletions pages/clustering/high-availability/setup-ha-cluster-k8s.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1692,6 +1692,27 @@ Notes:
A ready-to-use example values file is available in the Helm charts repository:
[`examples/remote-monitoring/values-ha-k8s-metrics.yaml`](https://github.com/memgraph/helm-charts/blob/main/examples/remote-monitoring/values-ha-k8s-metrics.yaml).

#### Example Grafana dashboards

Example dashboards for visualizing the shipped metrics and logs are available in the
Helm charts repository under
[`examples/dashboards/`](https://github.com/memgraph/helm-charts/tree/main/examples/dashboards):

- [`memgraph_openmetrics.json`](https://github.com/memgraph/helm-charts/blob/main/examples/dashboards/memgraph_openmetrics.json) —
Memgraph metrics scraped directly from the OpenMetrics endpoint
(`scrapeMemgraphDirectly: true`). This is the same dashboard that
`prometheus.grafanaDashboard.enabled: true` ships as a `ConfigMap`.
- [`memgraph_victorialogs.json`](https://github.com/memgraph/helm-charts/blob/main/examples/dashboards/memgraph_victorialogs.json) —
Memgraph logs shipped by `vectorRemote` and queried from VictoriaLogs.

Import them in Grafana via **Dashboards → New → Import**. Both use datasource template
Comment thread
vpavicic marked this conversation as resolved.
Outdated
variables, so after importing pick your Prometheus-compatible datasource ("Metrics data
source") and, for the logs dashboard, your VictoriaLogs datasource ("Logs data source").
Their filters are driven by the `cluster_id`, `cluster_env` and `service_name` labels you
set in `vmagentRemote.externalLabels` and `vectorRemote.extraLabels`; the dashboards also
break metrics and logs down per instance, so you can compare coordinators and data
instances in the same view.

## Configuration options

The following table lists the configurable parameters of the Memgraph HA chart
Expand Down
19 changes: 19 additions & 0 deletions pages/getting-started/install-memgraph/kubernetes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -454,6 +454,25 @@ Notes:
A ready-to-use example values file is available in the Helm charts repository:
[`examples/remote-monitoring/values-standalone-k8s-metrics.yaml`](https://github.com/memgraph/helm-charts/blob/main/examples/remote-monitoring/values-standalone-k8s-metrics.yaml).

##### Example Grafana dashboards

Example dashboards for visualizing the shipped metrics and logs are available in the
Helm charts repository under
[`examples/dashboards/`](https://github.com/memgraph/helm-charts/tree/main/examples/dashboards):

- [`memgraph_openmetrics.json`](https://github.com/memgraph/helm-charts/blob/main/examples/dashboards/memgraph_openmetrics.json) —
Memgraph metrics scraped directly from the OpenMetrics endpoint
(`scrapeMemgraphDirectly: true`). This is the same dashboard that
`prometheus.grafanaDashboard.enabled: true` ships as a `ConfigMap`.
- [`memgraph_victorialogs.json`](https://github.com/memgraph/helm-charts/blob/main/examples/dashboards/memgraph_victorialogs.json) —
Memgraph logs shipped by `vectorRemote` and queried from VictoriaLogs.

Import them in Grafana via **Dashboards → New → Import**. Both use datasource template
Comment thread
vpavicic marked this conversation as resolved.
Outdated
variables, so after importing pick your Prometheus-compatible datasource ("Metrics data
source") and, for the logs dashboard, your VictoriaLogs datasource ("Logs data source").
Their filters are driven by the `cluster_id`, `cluster_env` and `service_name` labels you
set in `vmagentRemote.externalLabels` and `vectorRemote.extraLabels`.

### Node affinity

The chart exposes the full Kubernetes `nodeAffinity` spec via the `nodeAffinity`
Expand Down