Any issues with including NetData on the root server and as an app add-on?
-
@cvachery said in Any issues with including NetData on the root server and as an app add-on?:
Infos I can give :
Command used to install : cloudron install --image cvachery/netdata-app:v1.44.1
Github : https://github.com/aylham/cloudron-netdata
Docker image : docker pull cvachery/netdata-app:v1.44.1
Netdata doc on how to setup streaming : https://learn.netdata.cloud/docs/streaming/understanding-how-streaming-works#enable-streaming-between-nodesDo you provide the CloudronManifest.json somwhere?
-
@Kubernetes it's in the repo at https://github.com/aylham/cloudron-netdata
-
@d1rk This application package not being officially supported by the team, it means you'd need to follow the instructions from that package repo. However, you could use https://docs.cloudron.io/packaging/tutorial/ as an example of what installing a custom application looks like.
-
@cvachery this might be a general Cloudron backup issue. Does netdata create a lot of temporary files? If possible, change the directory where it changes those files to be outside the backup (like in /run or /tmp). A fix from the Cloudron side is coming (it's a bit complicated since we have to rewrite/replace a node module).
-
@cvachery said in Any issues with including NetData on the root server and as an app add-on?:
What would be the next steps to integrate it directly into Cloudron AppStore?
this is only blocked by us we have a bunch of requirements for packages like having tests etc. So, each package takes time to get polished. If you are in the market for writing the tests, that will help speed things up definitely. But this is on top of the list for us (cc @vladimir-d )
-
@cvachery In your package, do you see the (cloud) Login button on the top right after one logs in with ProxyAuth ?
-
@cvachery ok, thanks. The whole thing is quite confusing because you see the Login button after logging in
-
I know but that's because the cloudron login is just the proxyauth but that login button is for the cloud. There is no auth by default to access to webui (hence why I use the proxy auth)
The whole netdata UX is made to make you move to the cloud
Trying to clean that button (bumping to 1.45.0 at the same time) -
@cvachery I am trying to get the netdata package out at https://git.cloudron.io/cloudron/netdata-app/ . Just comparing yours and the one that @vladimir-d has. Will make an unstable, but the netdata UX is not ideal, hmm.
-
Just tried the current state of this package and mostly this seems to work. There is a ton of graphs and all, no clue who needs all this, but looks good for sure.
Before we get this out, can anyone here answer how this works in terms of public/private pages? By default all metrics are public and one can only hide them when logging into their https://app.netdata.cloud offering and binding that to the self-hosted one. Although actually https://app.netdata.cloud is essentially the same as the self-hosted. Further status links point to the upstream offering. All in all this looks a bit like the selfhosting is just an afterthought, but maybe I am mistaken, so anyone with more clarity on this, please shed some light on the topic.
-
@nebulon https://forum.cloudron.io/post/85552
as far as I know the agents have a GUI unsecured, but when installing on Cloudron you can App proxy them to secure. Then you can default "connect" them to the Netdata Cloud or change the config to "connect" them to your own central Agent that is "collecting" the data streams from itself and the connected agents.
-
By default every agent can dispaly a dashboard for itself. You can however stream your metrics to a
parent
node and deactivate the web interface in the children nodes.
This is the way I'm using it at the moment, my parent node is on Cloudron and all my children stream their metrics to it. The auth is done with an API key ( doc here )
I'm not sure actually how my metrics are reaching netdata behind the ProxyAuth. Maybe they stream as UDP and the proxy is only for TCP? -