Blackbox Exporter on Cloudron ?

timconsidine — Sun, 22 Jun 2025 11:51:30 GMT

Will give it a go

What port do Prometheus listen on, for Grafana to connect?

jadudm — Sun, 25 May 2025 19:18:38 GMT

For anyone doing a setup on Cloudron, I found my way here. I was specifically trying to set up monitoring of a Minio instance on my installation. Install Prometheus normally. No special configuration is needed. When you do mc admin prometheus generate ALIAS, you will need to make sure you set that alias up as having enough permissions to actually read everything. Using an alias that has limited access controls (e.g. read-only on a single bucket) will not work; Prometheus will not be able to query the Minio API. Once Prometheus has a positive health check on the Minio instance, you can then set up Grafana. Install normally. When you add Prometheus as a data source, per above, just use the HTTPS URL of the Prometheus installation on Cloudron. No port is needed. The user must be a valid cloudron user. You might want to create a new cloudron user called "prom-graf" or similar, and only give that user permission to access Prometheus. This is just to isolate the access from (say) a standard account you use for all your other tasks/work. Add that username and password in the "basic auth" section. At this point, you can add some dashboards. I used the "import" option, and copy-pasted JSON from these dashboards: https://grafana.com/grafana/dashboards/13502-minio-dashboard/ At that point, I had dashboards living for my Minio installation. I have no idea yet what log volume will look like, or rotation, or... or... but, I might update this thread (or start another) later as I discover those things. I found myself having to dig around for this information/experiment. Perhaps I just didn't read the correct docs.

SNMP exporter to a local Prometheus server?

jediD83 — Mon, 31 Mar 2025 01:32:17 GMT

@joseph No worry joseph. Thank for the help though.

Prometheus can't reach node exporter (Blocked traffic)

abset — Tue, 11 Feb 2025 18:44:04 GMT

Thanks for your reply. We are monitoring some Cloudron metrics with Prometheus (e.g. disk space). What's implied from what you say makes sense from the security point of view. We have to think about how to monitor Cloudron using different methods.

Is there a reason why Prometheus chunk file size getting increased overtime?

girish — Fri, 19 Jan 2024 04:48:16 GMT

@agitk this is the Cloudron forum . Here we discsus the Promotheus package of Cloudron . Are you using Cloudron for hosting Prometheus? But regardless, app questions are probably best asked in https://github.com/prometheus/prometheus/discussions (I think).

Adding remote targets in prometheus.yml

BrutalBirdie — Fri, 15 Dec 2023 16:37:31 GMT

please post your yaml with removed / redacted sensitive information in a code block and not plain. You can also always use e.g. : job_name: scrape_interval: 5s static_configs: - targets: ['

Network statistics report container instead of host with node_exporter

lcd_official — Mon, 13 Nov 2023 15:56:14 GMT

@girish Hi Girish! So I could totally be misreading this, but after some testing, it really does look like CPU and Mem stats do come through from the underlying host... Here is what I tried to confirm this. Let me know if I am way off base and I'm missing something crucial. First, just base observations: Prometheus reports back 4GB of total system memory, much more than the 512MB I have allocated for the Prometheus app container itself. Most of the time, the CPU utilization of my host VPS hovers around 2-3% as reported by Prometheus data, whereas the (according to Top) CPU utilization of the container is 1-2.5% Graphs on my VPS provider's control panel roughly correlate to the CPU utilization observed in Prometheus data. Second, based on stress-testing Using Stress to stress-test individual CPUs or all CPUs to 100% in the host system correctly registers corresponding observations in Prometheus data. Using Stress -vm within the Prometheus app container to take up 256MB of RAM correctly registers a ~256MB bump over existing baseline memory observations from Prometheus data, and not 50+% utilization as would be expected if the container stats were being reported (container has 512MB allocated to it). Using Stress -vm out on the host system to chew up 2 GB of memory correctly shows a ~2GB increase in memory utilization reported by Prometheus data. So far CPU, Mem, and Network stats are all that I have played with, and Network is the only one so far that I can confirm positively does only report the container stats instead of the host system. Not having correct network stats isn't a deal-breaker for me (though it would be nice, but not if doing so would put the system at risk of a container breach). I thought I'd at least report my findings thus far for anyone else that stumbles upon this. Anyway, even if I am wrong, I have had a real great time playing with this! Thanks for making it all possible!

Prometheus.yml file does not appear to work and other config is read-only

lcd_official — Tue, 07 Nov 2023 00:38:03 GMT

@girish Pefect. As always, thank you for the quick response!

Change feature flag of prometheus

girish — Tue, 11 Jul 2023 11:14:10 GMT

I have adjusted the latest package to make CLI args customizable (since there's no way to do this via env vars).

Basic auth for incoming requests

girish — Sun, 19 Mar 2023 09:55:53 GMT

@JLX89 prometheus app already supports proxyAuth . Can you check with a new installation ? We even have basic auth turned on.

Track installed apps

Jan Macenka — Wed, 04 Jan 2023 22:50:13 GMT

Blocking /metrics and /health endpoints for Apps by default I'd also like to track Jellyfin which I love to run as an cloudron App. It comes with pre installed Prometheus endpoint according to the documentation which I'd like to use. The default Cloudron-location for this file is /app/data/jellyfin/config/system.xml However I dont want to expose this endpoint to the public Internet. Any Ideas how I could prevent this? If we find a good solution, I think it would be best to have the /metrics and /health endpoints blocked by default because Cloudron-Admins most likely dont want to expose these to the Internet anyway. @girish would you have an Idea where I could apply such a config change? Best regards and thanks for the answer in advance PS: Will gladly contribute to the Documentation as we found a good solution. I just fell down the rabbit hole to a certain degree in advancing my home-lab more towards a real data-center

Prometheus - Cannot login

vishnumadhusoodanan — Wed, 26 Oct 2022 04:46:17 GMT

Thanks @girish and sorry for the late reply

Adding local targets to Prometheus

girish — Tue, 04 Oct 2022 22:57:08 GMT

@cortex said in Adding local targets to Prometheus: How do I add the other Cloudron apps to the targets to monitor them? I don't have much idea here, maybe @eriktad or @BrutalBirdie knows. In general, what is needed to add a target to Prometheus? IP Address?

Prometheus + Grafana actually working

girish — Fri, 29 Apr 2022 03:59:15 GMT

@lcd_official indeed, prometheus_variables.sh is obsolete by now. Use env.sh instead.

Add option for users to add starting parameters

nebulon — Wed, 08 Sep 2021 08:33:47 GMT

@brutalbirdie thanks, I merged it and made a new package release.

Configure prometheus.yml file

kenjoo — Thu, 01 Apr 2021 13:52:53 GMT

@fbartels it works, thanks!

Cloudron System Backup Blocked By Prometheus

girish — Mon, 01 Mar 2021 19:55:24 GMT

@Jan-Macenka yeah, there's some bug in the fs module we use . We are replacing it next release, so maybe this bug goes away.

Ownership of the /app/data directory not set to cloudron:cloudron

girish — Thu, 10 Dec 2020 14:15:06 GMT

@christophermag This should be fixed now.

Prometheus - Package Updates

Package Updates — Wed, 11 Nov 2020 00:51:36 GMT

[1.15.2] Update alertmanager to 0.32.2 Full Changelog [BUGFIX] Fix dispatcher goroutine leaks on destroyed alertgroup swap. #5241