MetricGenerator, but the
Metricstruct does not include the timestamp.
Topology, is seems that the timestamp for the host consumption is set to the point when record are generated (
refresh_record) which is not the time when the measurement are actually read , is there a reason for that ?
gen_all_metricsis only used by the prometheus exporter, sdout json and riemann exporters all implement their own logic for process consumption (which is for me the most important metric)
That's a good point, we needed some specific behavior for the riemann exporter so we didn't used the generic function. We should definitely find a cleaner way to do that.
The power consumption calculation for each process could be easily moved to MetricGenerator though, as it only requires to have access to both the topology and ProcessTracker.
Hi there !
I felt like we had many topics on going and one could be a bit lost about what's going on and what PR should be merged first etc.
I wrote a quick "monthly report" here
I encourage you to discuss on that thread for everything related. It seems to me this is much more readable than the chat on the long term.
please also tell me if this adds value or not, and why. I'd like to make the management of the project more transparent.
Working on #109 I've changed a bit the way MetricGenerator can be used. It now owns the Topology struct (it held a reference previously). It makes easier having the MetricGenerator struct instantiated outside of the loop of most exporters and thus optimize performances (holding counters for instance to create some cache-like mecanisms). My case was with prometheus exporter, when using --containers, to not query the docker socket to often.
Please have a look if your are interested. A company interested in the feature (extra labels for processes metrics when in a docker container) will test it before I merge. Feel free to tell me your thoughts about this (and the feature) in the mean time.
Do you use scaphandre in CI ?
I would like to measure the energy consumed by a test suite to get a kind of power score for different iterations of an application code.
My naive approach is the following: