![]() Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
![]() There are no comments
There is nothing attached to this issue
This issue has no duplicates
There are no code checkins for this issue |
|||||||||||||||||||||||||||||
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
In any case, that's not the main problem. The problem with thermal sensors is that there is no standard protocol to access them. It depends on the hardware you have, how the device drivers interact with it, and whether the OS can access the functionality. Furthermore, you'd need some way to access thermal readings from Java, which adds yet another layer of complexity. Plus, hardware specifications change all the time and there would be a huge maintenance cost. Due to all this, I have no intention to implement this specific type of monitoring.
However, what I can propose, and which I think would benefit the whole JPPF community, is an extension point to inject custom monitoring data (i.e. additional columns) in the "JVM health" view of the console. Note that you already have the possiblity to customize the admin console, along with the servers and nodes, to add custom monitoring:
beiri22 wrote:
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?