@humptydumpty to reliably update i ended up always updating the docker tag to the desired version. With the tag updated you just need to run flyctl deploy again.

STATSD_URL=udp://127.0.0.1:8125

So the above is the correct value for Cloudrons?

@vladimir-d DBeaver Database Dashboard? Or you thinking longer timeframe and more detail?

@mdreira said in Lightmeter - Mail server delivery monitoring:

What mail server does Cloudron use? Exim?

This is what Cloudron uses for smpt: https://haraka.github.io/

Right.. It seems there are many candidates zabbix, netdata, some SNMP thing I forget etc. I prefer simply making sure Cloudron "works" with these existing software. It's why we added a way to open up the firewall as well. Happy to make any more fixes required to make these things work more easily.

@shai There may also be a plugin that does this too - it's worth trying to search on Nextcloud's own store-front for plugins.

@hillside502 yes, would be cool to map home networks and the upcoming Cloudron Multiserver.. and any ActivityPub App federations.

@atrilahiji That'd be the tax monitors, they soon format c: your bank account if you stop pinging their servers 😱

PSPS. I hope no one takes any disrespect when having opposing ideas on here. I always try to debate in good faith. I view us, the forum members, as needing to decide on important infrastructure aspects like this. So it’s us vs the problem. Not my idea vs anyone else’s. The problem is that sometimes users have to repair their apps manually. It usually happens after auto-updates / reboots (the only two times I’ve experienced it or read about others experiencing it on here). So what’s the solution? My solution is to auto-repair apps like that until we get enough data to fix the underlying problem. Meaning, we need not only an auto-repair so we’re not punishing users for a bad update (that will always happen), but also despite automatic repairs, easier log reporting of these errors to us.

So, it’s us vying for more logs to fix underlying issues, and automatic repair when something really is a one-ff situation which sometimes don’t have an explanation. Or they do but an average user couldn’t find it. But if they hit the “Send us crash logs” button then we might be able to fix it or find the issue.

If I understand correctly, you are asking for some netdata configuration. I will leave it open anyway in case some of our forum users can help. But maybe it's better suited in their forum.

In the past, I think people have recommended integrating with netdata. I don't have experience with netdata but wanted to throw the idea out there.

Other than that, current graphs is rendered using data collected by graphite/carbon.

In Cloudron 5.6, we added a way to whitelist additional incoming ports - https://docs.cloudron.io/networking/#whitelist-ports