netdata - real-time monitoring
-
This app will make a huge difference on Cloudron server as I’m currently missing real-time insights in ie. CPU, network I/O, etc
It looks like it’s really easy to install or setup but I’m not familiar (yet) with creating Cloudron apps.
@nebulon what are you guys using for real-time server monitoring?
BTW: their new GIT is https://github.com/netdata/netdata/wiki
-
@imc67 said in netdata - real-time monitoring:
I’m not familiar (yet) with creating Cloudron apps.
Have you read the packaging tutorial?
(which imho needs to be easier to find from the main Cloudron website):https://cloudron.io/documentation/custom-apps/tutorial/
@imc67 said in netdata - real-time monitoring:
I’m currently missing real-time insights in ie. CPU, network I/O, etc
I get all those on my Hetzner cloud over in the Hetzner console. Perhaps your server/ VPS provides this info too?
-
@jdaviescoates yes DO has also some metrics but not real-time and not so extensive and expandable as Netdata.
About packaging, yes of course I've read those but that doesn't mean you're able to create it immediately
-
@jdaviescoates said in netdata - real-time monitoring:
Have you read the packaging tutorial?
(which imho needs to be easier to find from the main Cloudron website):
https://cloudron.io/documentation/custom-apps/tutorial/I blindly followed the tutorial and it result this:
https://hub.docker.com/repository/docker/jodumont/netdata
and the repo is there: https://git.cloudron.io/jodumont/netdata-app -
@JOduMonT said in netdata - real-time monitoring:
https://hub.docker.com/repository/docker/jodumont/netdata
and the repo is there: https://git.cloudron.io/jodumont/netdata-app@nebulon does this count for "a free license for Your App Community" ?
-
@JOduMonT it seems you have just forked the tutorial app and copied things from the upstream netdata Dockerfile. If you actually want to create a Cloudron app package for netdata, then you would have to revisit the package files. For example
VOLUME
in Dockerfile is not supported, also none of the CloudronManifest.json meta information seems to have been applied to netdata. Also healthcheck is not implemented.
Generally it may be nice to have netdata if it provides useful information and is actually be packaged for Cloudron. -
@nebulon said in netdata - real-time monitoring:
@JOduMonT it seems you have just forked the tutorial app and copied things from the upstream netdata Dockerfile. If you actually want to create a Cloudron app package for netdata, then you would have to revisit the package files. For example VOLUME in Dockerfile is not supported, also none of the CloudronManifest.json meta information seems to have been applied to netdata. Also healthcheck is not implemented.
Generally it may be nice to have netdata if it provides useful information and is actually be packaged for Cloudron.thanks for the guidance,
it was my first 10 minutes
I'll have more time next week. -
-
-
Just leaving a link here since I struggled a bit to find it again. https://forum.cloudron.io/post/82867 has a package from @cvachery
-
@marcusquinn Yeah, that demo does look very good.
-
@imc67 @marcusquinn are you still using netdata? If so, are you using the selfhosted dashboard or the dashboard in the cloud ?
Also, in the demo that marcus linked, it says "Your Agents are open by default. Secure them easily with Netdata Enterprise Agent." at the top. What does this mean? I thought agents are reporting something and you cannot query agents. Why are they open by default and can they only be secured with enterprise version?
-
@girish I still use Netdata installed on all three Cloudron servers + 3 RPI's.
On Cloudron I access them via AppProxy so they are secured. Then all the Agents are currently connected to the Netdata Cloud and I can see them all in one dashboard.
I don't know what Enterprise Agent is?
As far as I know agents are streaming data to the local webGUI or to the Netdata Cloud GUI.
-
Thanks. I guess we need to educate people that the Login button logs into the cloud in the POSTINSTALL.
-
@cvachery we have to revisit this. We got blocked by the possibly confusing Login button appearing on the top right after logging in. I guess we have to live with it?
-