Description of problem: Document what statistics and logs data do we collectd from the hosts and engine machines
Assigning to Emma for review. Emma, this is closely related to bug 1451625. You may find it easier to work on these two tasks in a single bug, in which case feel free to close this one and track everything in bug 1451625.
Upstream documentation http://www.ovirt.org/develop/release-management/features/engine/metrics-store/
I'm untargeting this bug pending proper docs team triage. Shirly, if you have further information, please feel free to add it to this bug.
TRACKER BUG - individual bugs will be opened per plugin and for the logs. The effort here is for 1. Logs 2. Plugins responsible for collecting metrics. LOGS ==== There are two logs - engine and vdsm. Need to be documented and add links to the current documentation after verifying that this is enough to create reports and understand what is being displayed. (original effort 4d) PLUGINS ====== There are 14 plugins each of which have several sub-categories. All of which must documented. After analyzing the available full documentation from signalfx [1], which uses an Apache license and therefore can be reused, I have come up with the following information. Plugins covered by Signalfx docs and therefore requiring "less" documentation effort: (original estimate 2d per plugin) disk interface df memory swap load postgresql Plugins NOT covered by Signalfx docs that require a much greater documentation effort: (original estimate 4d per plugin) NFS Processes CPU VIRT Entropy Swap vm statsd [1] https://github.com/signalfx/integrations
(In reply to Emma Heftman from comment #5) > TRACKER BUG - individual bugs will be opened per plugin and for the logs. > > The effort here is for > 1. Logs > 2. Plugins responsible for collecting metrics. > > LOGS > ==== > There are two logs - engine and vdsm. Need to be documented and add links to > the current documentation after verifying that this is enough to create > reports and understand what is being displayed. (original effort 4d) BZ#1513032 > > PLUGINS > ====== > There are 14 plugins each of which have several sub-categories. All of which > must documented. > > After analyzing the available full documentation from signalfx [1], which > uses an Apache license and therefore can be reused, I have come up with the > following information. > > Plugins covered by Signalfx docs and therefore requiring "less" > documentation effort: (original estimate 2d per plugin) > disk > interface > df > memory > swap > load > postgresql > > Plugins NOT covered by Signalfx docs that require a much greater > documentation effort: (original estimate 4d per plugin) > NFS > Processes > CPU > VIRT > Entropy > Swap > vm statsd > > > [1] https://github.com/signalfx/integrations
We are looking to get a simple list for the MVP, full details can be added later on.
That tracked in 1518561.
After further analyzing the available documentation from both Signalfx and colectd's wiki,the situation is as follows: Available documentation: disk > interface > df > memory > swap > load > postgresql NFS - 21 /69 will be split into two sep. bugs. Limited documentation: Process Most of NFS statsd
*** Bug 1475819 has been marked as a duplicate of this bug. ***
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
*** This bug has been marked as a duplicate of bug 1451625 ***