Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1508921

Summary: [Test-Only] Check fluentd resource consumption when collectd_interval is 10s vs 20s (depends on bug 1478695 )
Product: [oVirt] ovirt-engine-metrics Reporter: Shirly Radco <sradco>
Component: GenericAssignee: Shirly Radco <sradco>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.7CC: bugs, sradco
Target Milestone: ovirt-4.2.0Keywords: Performance, TestOnly
Target Release: ---Flags: rule-engine: ovirt-4.2+
lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:09:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1478695    
Bug Blocks:    

Description Shirly Radco 2017-11-02 14:00:36 UTC
Description of problem:
Check fluentd resource consumption when collectd_interval is 10s vs 20s

Comment 1 Yaniv Kaul 2017-11-02 16:30:06 UTC
(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.

Comment 2 Shirly Radco 2017-11-06 20:41:18 UTC
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

Comment 3 Lukas Svaty 2017-12-14 15:37:17 UTC
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

Comment 4 Sandro Bonazzola 2017-12-20 11:09:59 UTC
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.