Any issues with including NetData on the root server and as an app add-on?

[girish]

@cvachery thanks, will take a look next week or so!

[cvachery]

Hello @girish,
Any chance you had time to have a look a this?

[girish]

@cvachery not yet, but it's on our list.

[Kubernetes]

@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-nodes

Do you provide the CloudronManifest.json somwhere?

[girish]

@Kubernetes it's in the repo at https://github.com/aylham/cloudron-netdata

[cvachery]

And hopefully it will do the job.
I use my package as a parent node since I released it without any issue but more usage will be helpful

[d1rk]

Sounds promising. Can someone please share how to install this app on my Cloudron? Thank you.

[Lanhild]

@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]

After to be honest I'm encountering an issue that is the backups aren't working for some reason.
Does someone who installed my package have this issue too. Or is it just from my install?

[girish]

@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]

After update and reboot of the Cloudron backup seems to be working OK now. So probably the bug you said on Cloudron side.

What would be the next steps to integrate it directly into Cloudron AppStore?

[girish]

@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]

@girish Depending of the tests I can have a look and maybe give it a try if that can help you

[cvachery]

Just to let you know that I updated my package to add the sendmail package (to enable email notification) and bump the upstream version to 1.44.3

[girish]

@cvachery In your package, do you see the (cloud) Login button on the top right after one logs in with ProxyAuth ?

[cvachery]

Yes I do, I did not succeed to get rid of all the cloud bits and pieces as it is pretty much all over the software here and there.
I tried this doc but was unsuccessful

[girish]

@cvachery ok, thanks. The whole thing is quite confusing because you see the Login button after logging in

[cvachery]

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)

[girish]

@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.

[nebulon]

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.