Hi Sandro,
Thank you a lot.
Jirka
On 2/12/24 13:20, Sandro Bonazzola wrote:
Hi, thanks for reporting.
An advisory has been published:
https://github.com/oVirt/ovirt-engine/security/advisories/GHSA-5p2q-85hp-rvxg
and the fix has been released in ovirt-engine-4.5.6:
https://github.com/oVir
hi,
i have prometheus based ovirt hosts monitoring (node_exporter,
smartcl_exporter, ipmi_exporter)
https://prometheus-community.github.io/ansible/branch/main/ and alerts
from https://samber.github.io/awesome-prometheus-alerts/
after i started this monitoring i found that one VM is overloa
For detailed monitoring I use Zabbix. This way I get detailed metrics
on my hypervisors, VMs as well as my network storage.
If a machine starts generating large IO I get alerts highlighting the
responsible machine as well as the impacted services. For example, you
might get high IO on a VM
Hi.
I also use Zabbix here. Its problem is that it collects metrics in real
time, this is not its function.
There are other alternatives like Elasticsearch + metricbeat, but from what
I've tested, it's very heavy and uses a lot of disk space lol.
I never used Prometheus, I found it interesting. I
I have different collection schedules depending on the importance of the
data i'm collecting. You can adjust as you need accordingly.
For your IO issues you can easily simply poll your machine's IO load
statistics from the 5/10/15 minute averages. That will not give you
precise intervals but
5 matches
Mail list logo
