Description of problem: Collectd default interval is 10 seconds. We want to add an collectd_interval parameter that will allow changing the interval as needed when running the metrics ansible.
I think it should be 15 seconds, to match VDSM's interval.
(In reply to Yaniv Kaul from comment #1) > I think it should be 15 seconds, to match VDSM's interval. The interval in VDSM is 3 seconds I believe. 15 seconds is for engine pulling. I think we would be better off with 20 seconds to match the DWH collection rate.
(In reply to Yaniv Lavi (Dary) from comment #2) > (In reply to Yaniv Kaul from comment #1) > > I think it should be 15 seconds, to match VDSM's interval. > > The interval in VDSM is 3 seconds I believe. 15 seconds is for engine > pulling. > I think we would be better off with 20 seconds to match the DWH collection > rate. DWH collection sampling was changed to 60 seconds. Want to reconsider?
DWH is for long term storage and metrics is also for monitoring. Different needs.
Testing has indicated this request is declined. You may appeal this decision by reopening this request.
Fixing the mess I made, apologies
Moving back to ASSIGNED as the patch has this comment: "There is a limitation to setting the interval in /etc/collectd.d/, the plugins that are pre-loaded in /etc/collectd.conf remain with the same interval that is set in that file or the with the default 10 seconds"
Didi has fixed the issue in centos-opstools. https://review.rdoproject.org/r/#/c/9802/ Packages needs to be built before this bug can be
**Packages needs to be built before this bug can be fixed and tested
This RFE adds a top level configuration role to collectd that allows setting collectd interval with a parameter. It depends on Didi's patch to collectd packaging. Until it is available the parameter will be applied to the plugins that are loaded after the file 05-global-configurations.conf. oVirt plugins are loaded after this file.
verified 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.