prometheus-podman-exporter VS net-test

Hey, I have homelab NUC server where I run different services as rootless podman pods and containers running by dedicated users, eg. nextcloud pod running by nextcloud user, gitea by gitea, znc by znc and more. Next step was trying to monitor these services. First trey was using cockpit-podman feature, but in UI I see only containers of my user and rootfull which both was empty. I cannot switch to another user because the're not capable for login to cockpit. Now I'm testing prometheus and podman-exporter which seems ok, but again I see containers only if I run prometheus-podman-exporter service as user who run another podman container (e.g. as nextcloud user). Of course I can run this service parallel as dedicated user with another port and add them as target to prometheus scrape config but from obvious reason I want to avoid that. Is it more gentle way to monitor my pods? I know that those namespaces are one of the main feature of Podman but I don't consider this before my deploys :)

Cool! It's so funny I just recently took an old bash script of mine which did something similar and have been upgrading it into a proper application which exports metrics to Prometheus and Grafana: https://github.com/Noah-Huppert/net-test

I saw a comment below where some was rolling their eyes that you "complicated" stuff with Prometheus, Grafana, and Docker and how you could just use Bash scripts and crons. As I just upgraded my codebase from this more bare metal approach to this "more complex setup" I'd like to mention: there's no way you could do time series statistical analysis easily with "just a cron job and a bash script". Prometheus and Grafana are for more than just buzz words. Prometheus offers an advanced time series database which allows you to, at minimum, do more robust analysis using data techniques like Histograms. As for Grafana, it makes exploring data dead easy. Providing users with a Docker Compose setup is also something I did with my tool and the benefits are huge. It lets me distribute a setup which relies on multiple moving parts working smoothly together. Sure I could write a whole wiki on how you should setup Prometheus Grafana and my tool, or I could distribute the setup with a configuration as code tool. Ensuring that even if someone doesn't want to use Docker Compose they can at least read my configuration as code and see exactly what I did to setup my tool.