For the complete documentation index, see llms.txt. This page is also available as Markdown.

Infrastructure health

1. Introduction

OpenCRVS monitoring tools let you measure and view critical metrics such as available disk space, used memory, and total CPU load. This information can be used to proactively increase available resources when demand increases.

These metrics are collected by a tool called Metricbeat and stored in Elasticsearch.

2. Common infrastructure metrics

The following list summarises the most important infrastructure metrics to monitor:

  • CPU usage

  • RAM usage

  • Network RX/TX

  • Disk usage usage / IOPs

Navigate to Observability > Infrastructure > Hosts:

3. Kubernetes metrics

Navigate to Observability > Infrastructure > Infrastructure inventory:

  1. Change "Show" selector to "Kubernetes"

  2. Change Presentation view to "Table"

  3. From dropdown choose metric

4. Accessing metrics from Explorer

To view infrastructure metrics, log in to Kibana and navigate to ObservabilityMetricsMetrics Explorer.

In this view, you can:

  • See current usage of different resources

  • Group metrics by host, service, or other dimensions

  • Filter and visualize data over time

5. Available disk space

To see the amount of available disk space, navigate to Metrics Explorer (Observability → Metrics → Metrics Explorer).

You can see the current usage of different storage devices by selecting:

  • Value: Max of system.filesystem.used.pct

  • Grouped by: host.hostname and system.filesystem.device_name

Filtering for encrypted data storage

The default installation of OpenCRVS uses an encrypted disk for data storage on all nodes named /dev/mapper/cryptfs.

You can filter the listed devices to only show these disks by using the following search clause:

system.filesystem.device_name : "/dev/mapper/cryptfs"

6. CPU usage

To monitor CPU usage:

  • Value: Average of [system.process.cpu.total](<http://system.process.cpu.total>).pct

  • Grouped by: host.hostname

This shows you the average CPU load across all processes on each host. Use a 24-hour timeframe to identify patterns and peak usage periods.


6. Memory usage

To monitor memory usage:

  • Value: average(system.memory.actual.used.pct)

  • Grouped by: host.name

This shows you memory usage per Host

Example for Kubernetes container filtered by namespace:

  • Metric: kubernetes.container.memory.usage.bytes

  • group per: container.name

  • Filter by: kubernetes.namespace


7. Read more

Last updated