diff options
| author | DShreve2 <david@netdata.cloud> | 2021-11-12 17:07:14 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-12 17:07:14 -0500 |
| commit | 1ddce5c3a1d69819f06319921cc8db2382922a3e (patch) | |
| tree | 69b91c8845e8897be24404d70a1bbf8d4c93cb3e | |
| parent | 3b5563ff081b3201431be0392ecb1c03ec44515e (diff) | |
Add command for new health entity file. (#11733)
| -rw-r--r-- | docs/guides/step-by-step/step-05.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/guides/step-by-step/step-05.md b/docs/guides/step-by-step/step-05.md index 30ab329cd8..8a4d084e4e 100644 --- a/docs/guides/step-by-step/step-05.md +++ b/docs/guides/step-by-step/step-05.md @@ -110,6 +110,13 @@ bother you with notifications. The best way to understand how health entities work is building your own and experimenting with the options. To start, let's build a health entity that triggers an alarm when system RAM usage goes above 80%. +We will first create a new file inside of the `health.d/` directory. We'll name our file +`example.conf` for now. + +```bash +./edit-config health.d/example.conf +``` + The first line in a health entity will be `alarm:`. This is how you name your entity. You can give it any name you choose, but the only symbols allowed are `.` and `_`. Let's call the alarm `ram_usage`. |