Description of problem: Check fluentd resource consumption when collectd_interval is 10s vs 20s
(In reply to Shirly Radco from comment #0) > Description of problem: > Check fluentd resource consumption when collectd_interval is 10s vs 20s Please specify how to configure it.
If you want to update the `collectd_interval`, you would need to run the Ovirt metrics configuration script like this: :: configure_ovirt_machines_for_metrics.sh -e "collectd_interval=20" or add the following line to the config.yml file and run configure_ovirt_machines_for_metrics.sh :: collectd_interval: 20
No big difference performance-wise, on engine machine and hosts collectd/fluentd did not get 10% of memory nor CPU. If you require something specific to test, feel free to put the bug back ON_QA. MemTotal: 3879824 kB 4 cores of processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Westmere E56xx/L56xx/X56xx (Nehalem-C) stepping : 1 microcode : 0x1 cpu MHz : 2526.998 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc rep_good nopl pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm tpr_shadow vnmi flexpriority ept vpid arat bogomips : 5053.99 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual tested in ovirt-engine-metrics-1.1.1-1.el7ev.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.