After updating to 1..45.4, I still cannot use thenetdata-claim.sh script

Not all functions require Cloud connection, seeAvailable Functions (Require Cloud column).

There it says:

Since these functions are able to execute routines on the node and due to the potential use cases that they can cover, our concern is to ensure no sensitive information or disruptive actions are exposed through the Agent's API.

I don't understand this. For example, both the Processes and Systemd-journal functions should be strictly read-only - so why is there a concern about "executing routines on the node"? Why doesn't other functions, like Block-devices or Mount-points, have this "problem"?

It feels like some functions are just arbitrary set to require Cloud, just to force people to create and connect their local nodes to a Cloud account...

Edit: additionally, "Processes", which requires Cloud, is handled by the plugin "apps". The documentation of "apps" even says:

Security

apps.plugin performs a hard-coded function of building the process tree in memory, iterating forever, collecting metrics for each running process and sending them to Netdata. This is a one-way communication, from apps.plugin to Netdata.

So, since apps.plugin cannot be instructed by Netdata for the actions it performs, we think it is pretty safe to allow it to have these increased privileges.

(https://github.com/netdata/netdata/tree/master/src/collectors/apps.plugin#security)

Just like most open source services, if it was actually "for security purposes", they can literally make it possible to register a local account and solve the entire issue once and for all.

Having to register your account ON THE CLOUD on its own is a bigf*ck you to security.

Having to register your account ON THE CLOUD on its own is a bigf*ck you to security.

^^ This. Might seem blunt but how true it is, honestly. I emailed Netdata using their Contact Us option – a few reps on Reddit said invite people wanting to discuss plan options and figure out s solution that works for them to use the contact form. I did so, and gave my argument, including my willingness to agree to create a Netdata Cloud account and link up my devices, IF I could secure my account with additional layers or security and also be able to link up all of my local devices under their free plan. 2 weeks later, I have not received a reply.

They're milking home users who probably aren't even their big money makers, and all of this new required plan stuff wasn't a thing a few years ago. If I was making money off their products, sure, I'll pay for it then, but I don't. I barely make enough money to pay myself, and some months, I don't even have money to do that.

One of the reps, somewhere on Reddit, had stated sometime ago, that Netdata is open source and anyone can modify the code, and for that matter, I could create my own account service. Yeah, ok, because I have that level of programming experience to roll my own accounts solution.

nice one! people certainly need a docker image of that!

nice one! people certainly need a docker image of that!

I found some metrics missing when running in docker (even after mounting all required files), so I install Netdata directly on host.

If you'd like to have a docker image, you can pull the Netdata repo, make the modification above and build it locally. It should be much easier to build locally with Docker. Dockerfile is located atpackaging/docker/Dockerfile.