diff options
Diffstat (limited to 'docs/monitor')
| -rw-r--r-- | docs/monitor/configure-alarms.md | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/docs/monitor/configure-alarms.md b/docs/monitor/configure-alarms.md index 4575b03ea1..2a977955b8 100644 --- a/docs/monitor/configure-alarms.md +++ b/docs/monitor/configure-alarms.md @@ -22,7 +22,8 @@ files. ## Edit health configuration files All of Netdata's [health configuration files](/health/REFERENCE.md#health-configuration-files) are in Netdata's config -directory, inside the `health.d/` directory. Use Netdata's `edit-config` script to make changes to any of these files. +directory, inside the `health.d/` directory. Navigate to your [Netdata config directory](/docs/configure/nodes.md) and +use `edit-config` to make changes to any of these files. For example, to edit the `cpu.conf` health configuration file, run: @@ -75,13 +76,18 @@ your systems, containers, and applications work. Read Netdata's [health reference](/health/REFERENCE.md#health-entity-reference) for a full listing of the format, syntax, and functionality of health entities. -To write a new health entity, use `edit-config` to create a new file inside of the `health.d/` directory. +To write a new health entity into a new file, navigate to your [Netdata config directory](/docs/configure/nodes.md), +then use `touch` to create a new file in the `health.d/` directory. Use `edit-config` to start editing the file. + +As an example, let's create a `ram-usage.conf` file. ```bash -sudo ./edit-config health.d/example.conf +sudo touch health.d/ram-usage.conf +sudo ./edit-config health.d/ram-usage.conf ``` -For example, here is a health entity that triggers an alarm when a node's RAM usage rises above 80%: +For example, here is a health entity that triggers a warning alarm when a node's RAM usage rises above 80%, and a +critical alarm above 90%: ```yaml alarm: ram_usage |