Replies: 1 comment 2 replies
-
|
We’ve actually received multiple requests in the past to include monitoring system. While the option to install Netdata has been available for a while (since v1.6.0), it was previously disabled by default. After carefully evaluating various monitoring tools, we settled on Netdata because it offers great visibility into system-level metrics and even some PostgreSQL-specific ones — to be honest, it’s one of the best monitoring tools we’ve seen so far. In practice, Netdata uses a relatively small amount of resources, and in most environments we barely notice its impact. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I wonder if
netdata_install: trueis a good default to have.Yes, it might be beneficial in some environments, however, I consider it more as an optional "nice to have" as a user if I really want it.
Maybe there can also be a dynamic default which is
truefor Console installs andfalsefor "automation" installs?The technical reasoning behind that is that
netdatarequires quite some CPU and about ~ 300MB memory at runtime. Most users might not even aware that it got installed and is running, consuming resources for no reason. Especially on small nodes this can be ~ 10% of the nodes total capacity.Last, if one sets
netdata_install: false,netdataisn't removed or disabled from the node again as there are no tasks to account for this.Beta Was this translation helpful? Give feedback.
All reactions