From 97e01009d69b8fbebfebf68f51e3d126d0ed43fc Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 30 Nov 2022 19:47:05 +0100 Subject: Merging upstream version 1.37.0. Signed-off-by: Daniel Baumann --- docs/guides/step-by-step/step-09.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'docs/guides/step-by-step/step-09.md') diff --git a/docs/guides/step-by-step/step-09.md b/docs/guides/step-by-step/step-09.md index 6333dfe69..8aacd7514 100644 --- a/docs/guides/step-by-step/step-09.md +++ b/docs/guides/step-by-step/step-09.md @@ -36,10 +36,10 @@ guide, your Netdata agent is already using the database engine. Let's look at your `netdata.conf` file again. Under the `[global]` section, you'll find three connected options. ```conf -[global] - # memory mode = dbengine - # page cache size = 32 - # dbengine disk space = 256 +[db] + # mode = dbengine + # dbengine page cache size MB = 32 + # dbengine disk space MB = 256 ``` The `memory mode` option is set, by default, to `dbengine`. `page cache size` determines the amount of RAM, in MiB, that @@ -56,10 +56,10 @@ space` based on your needs. The calculator gives an accurate estimate based on h metrics your Agent collects, and more. ```conf -[global] - memory mode = dbengine - page cache size = 64 - dbengine disk space = 512 +[db] + mode = dbengine + dbengine page cache size MB = 64 + dbengine disk space MB = 512 ``` After you've made your changes, restart Netdata using `sudo systemctl restart netdata`, or the [appropriate -- cgit v1.2.3