action #94753
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #92854: [epic] limit overload of openQA webUI by heavy requests
Try out munin on o3
Description
To have some statistical data, we could try out munin on o3.
It gathers data every 5 minutes and writes them in rrd format, and generates a daily, werkly, monthly and yearly graph for things like load, memory, disk usage, apache accesses, network traffic.
Todo:
- Install munin and configure
- Create restricted access over http for the team, since we don't want that data to be public
Updated by tinita over 3 years ago
Installed on o3:
# install
% zypper in munin munin-node
# config
% cd /etc/munin
% vim munin.conf
# configure hostname (e.g. openqa.opensuse.org)
# enable plugins
% cd /etc/munin/plugins
% for i in /usr/lib/munin/plugins/apache_*; do ln -s $i; done
% systemctl restart munin-node.service
HTML files are under /srv/www/htdocs/munin/ and not accessible from the webserver yet.
Apache would need the status module enabled for the apache_ plugins to work.
We also could enable some postgres plugins.
Updated by tinita over 3 years ago
Downloaded https://gallery.munin-monitoring.org/plugins/munin-contrib/postgres_queries3_/ plugin and put in /etc/munin/plugins/postgres_queries3_openqa
Configured in /etc/munin/plugin-conf.d/munin-node
We can now see the number of selects, inserts, updates and deletes (under the "db" category).
Updated by tinita over 3 years ago
- Status changed from In Progress to Resolved
Still todo:
- Enable apache status module to be able to collect statistics about apache requests/processes
- Make the generated HTML files available over the webserver, but only for "us", not for the public. Need to figure out how that can be set up in apache
These things are considered out of scope, so resolving this ticket
Updated by tinita over 3 years ago
Anyone wanting to look at the HTML pages, do this:
rsync -a o3:/srv/www/htdocs/munin ~/o3-munin/
(where "o3" is configured in your ssh config of course)
Updated by tinita over 3 years ago
- % Done changed from 0 to 100
- Estimated time set to 2.00 h
- Difficulty set to easy
Updated by okurz over 3 years ago
ok. If you like you can add the instruction to the wiki on https://progress.opensuse.org/projects/openqav3/wiki/#Infrastructure-setup-for-o3-openqaopensuseorg-and-osd-openqasusede
Updated by tinita over 3 years ago
The service was disabled by default, so it did not start with the reboot yesterday, so I enabled it.