diff options
author | Joel Hans <joel@netdata.cloud> | 2021-01-07 09:53:10 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-01-07 09:53:10 -0700 |
commit | 0bb7a429b619bc68104983691e4f957482630787 (patch) | |
tree | 040bc96ddd98ac59d7e83235f2babccc01ecb636 /docs/guides/configure | |
parent | 3adf54ff452fbe8216b64dfce9c7ec04bc7a270b (diff) |
Small updates, improvements, and housekeeping to docs (#10405)
* Fix Berkeley mentions
* Add new collectors to list
* Tweak Prometheus/OpenMetrics phrasing
* Fix heading depth in performance guide
* Clarify that exporting starts with Agent start
* Clarify usage of edit-config with new files
* Update images
* service -> systemctl
* Reverse systemctl order
Diffstat (limited to 'docs/guides/configure')
-rw-r--r-- | docs/guides/configure/performance.md | 11 |
1 files changed, 3 insertions, 8 deletions
diff --git a/docs/guides/configure/performance.md b/docs/guides/configure/performance.md index 24231fb81b..e542736a1d 100644 --- a/docs/guides/configure/performance.md +++ b/docs/guides/configure/performance.md @@ -52,7 +52,7 @@ Let's walk through the best ways to improve the Netdata Agent's performance. The fastest way to improve the Agent's resource utilization is to reduce how often it collects metrics. -## Global +### Global If you don't need per-second metrics, or if the Netdata Agent uses a lot of CPU even when no one is viewing that node's dashboard, configure the Agent to collect metrics less often. @@ -69,18 +69,13 @@ seconds, respectively. update every: 5 ``` +### Specific plugin or collector + Every collector and plugin has its own `update every` setting, which you can also change in the `go.d.conf`, `python.d.conf`, `node.d.conf`, or `charts.d.conf` files, or in individual collector configuration files. If the `update every` for an individual collector is less than the global, the Netdata Agent uses the global setting. See the [enable or configure a collector](/docs/collect/enable-configure.md) doc for details. -## Specific plugin or collector - -If you did not [reduce the global collection frequency](#global) but find that a specific plugin/collector uses too many -resources, you can reduce its frequency. You configure [internal -collectors](/docs/collect/how-collectors-work.md#collector-architecture-and-terminolog) in `netdata.conf` and external -collectors in their individual `.conf` files. - To reduce the frequency of an [internal plugin/collector](/docs/collect/how-collectors-work.md#collector-architecture-and-terminology), open `netdata.conf` and find the appropriate section. For example, to reduce the frequency of the `apps` plugin, which collects and visualizes |