Proof of concept of delegating monitoring to prmon #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Show how prmon can be used as an external resource monitor for jMonitor
and all of its children
current resource values
(using a new method, push())
This only a proof of concept to show the idea, I wouldn't use this code
in its current form.
The content of the current prmon snapshot file isn't quite a match to
what jMonitor uses, but it could rather easily be ammended (the final
prmon txt file does contain everything needed, but it's much more
awkward to parse on the fly).
In particular:
consuption time (user + system) so for now this has been used as a
proxy in the CPURate monitor.
so they are monotonic increasing; prmon could easily output the
correct snapshot values if needed
BEGINRELEASENOTES
exactly as it appears between the two bold lines
ENDRELEASENOTES