It should work. Please check if the configuration is applied - open http://<your host>:19999/netdata.conf and check if exclude space metrics on filesystems is correct and uncommented.
Okay, The problem was that old netdata instance was running even after executing systemctl restart netdata. same problem with systemctl stop netdata.
I had to force kill all netdata instance.
Now I can see that the netdata service does not kill the nginx instances it is running. Is that normal?
Nope, It was running after the installation, probably triggered by the installation script.
Right now, the Netdata instance properly stops and starts with systemd, but It is leaving behind lots of nginx worker process without their master process (zomie process most likely). And these can’t be killed.
Thanks for the clarification but It’s quite strange. These processes do not exist after a system reboot and only start after running netdata. Also these are running as netdata user, while my main nginx process runs as nginx user.
I’ve stopped main nginx instance but that does not kill these processes.