From 483926a283e118590da3f9ecfa75a8a4d62143ce Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 1 Dec 2021 07:15:11 +0100 Subject: Merging upstream version 1.32.0. Signed-off-by: Daniel Baumann --- docs/guides/step-by-step/step-05.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/guides/step-by-step/step-05.md') diff --git a/docs/guides/step-by-step/step-05.md b/docs/guides/step-by-step/step-05.md index 30ab329cd..8a4d084e4 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`. -- cgit v1.2.3