---
title: "Monitoring: Configuration"
description: "General monitoring configuration keys, and the configuration pages of the monitoring sections."
url: "https://docs.ravendb.net/7.2/monitoring/configuration"
version: "7.2"
---

# Monitoring: Configuration

> RavenDB publishes an official agent skill for coding assistants at https://docs.ravendb.net/skills/ravendb/SKILL.md (also installable with `npx skills add ravendb/skills`). The skill describes itself as: "Read this before writing any RavenDB query, client call or /databases/ request. Covers server setup, document modelling, the Node.js, .NET and Python clients, RQL, indexes, vector search and AI agents. Code written from recall tends to run and return the wrong rows, because RQL resembles SQL and the clients take field names as plain strings."

## Monitoring: Configuration

> **Note**
>
> - This page lists the general monitoring configuration keys, and points to the
>   configuration pages of the monitoring sections.
>
> - Learn how to set configuration keys in the [configuration overview](https://docs.ravendb.net/7.2/server/configuration/configuration-options.md).
>
> - In this article:
>   - [General monitoring keys](#general-monitoring-keys)
>   - [Per-section configuration pages](#per-section-configuration-pages)

## General monitoring keys {#general-monitoring-keys}

These keys control how the server collects its CPU and disk metrics:

### Monitoring.Cpu.Exec

A command or executable that provides RavenDB with CPU usage figures.  
RavenDB runs the command when the server starts, and continuously reads JSON objects with
`MachineCpuUsage` and `ProcessCpuUsage` fields (usage percentages) from the command's
standard output, using these values as its CPU metrics rather than measuring CPU usage itself.  
Note that the command must write to its standard output unbuffered.

---

#### Example: Reading CPU usage from a script

```json
{
    "Monitoring.Cpu.Exec": "/usr/bin/python3",
    "Monitoring.Cpu.Exec.Arguments": "/scripts/cpu_usage.py"
}
```

The script writes lines in this form to its standard output:

```json
{ "MachineCpuUsage": 57.0, "ProcessCpuUsage": 2.5 }
```

- **Type**: `string`
- **Default**: `null`
- **Scope**: Server-wide only

### Monitoring.Cpu.Exec.Arguments

The command line arguments for the `Monitoring.Cpu.Exec` command or executable.  
The arguments must be escaped for the command line.

- **Type**: `string`
- **Default**: `null`
- **Scope**: Server-wide only

### Monitoring.Disk.ReadStatsDebounceTimeInMs

The minimum interval between measures to calculate the disk stats.

- **Type**: `TimeSetting`
- **Default**: `1000`
- **Scope**: Server-wide only

## Per-section configuration pages {#per-section-configuration-pages}

Each monitoring section documents its own configuration keys:

| Section | Configuration page |
| - | - |
| Alerts and notifications | [Alerts and notifications: Configuration](https://docs.ravendb.net/7.2/monitoring/alerts-and-notifications/configuration.md) |
| Integrations (SNMP, OpenTelemetry) | [Integrations: Configuration](https://docs.ravendb.net/7.2/monitoring/integrations/configuration.md) |
| Logging | [Logging: Configuration](https://docs.ravendb.net/7.2/monitoring/logging/configuration.md) |
| Task errors | [Task errors: Configuration](https://docs.ravendb.net/7.2/monitoring/task-errors/configuration.md) |
| Tombstones | [Tombstones: Configuration](https://docs.ravendb.net/7.2/monitoring/tombstones/configuration.md) |
| Traffic watch | [Traffic Watch: Configuration](https://docs.ravendb.net/7.2/monitoring/traffic-watch/configuration.md) |
