You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then finally with this info, the data can be retrieved with stats.get_data with args [["dataset": "value", "source": "cputemp-0", "type": "temperature"]]
A lot of the sources are dynamic based on the system, like number of cpu cores (somewhat easy to handle), but then there are pool storage, jails, etc....
Also, I'm not sure how to decipher the units as there is no documentation. The CPU temperatures seem to be in deciKelvin units (is this a common unit for this?) but it is hard to know.
The text was updated successfully, but these errors were encountered:
disk temperature is one thing that is already integrated, FWIW
I was playing around with a subscription to reporting.realtime over the weekend, but was very perplexed as to what unit was the CPU temp reporting in (especially when compared to what the TrueNAS UI showed). I legit hadn't thought of something like deciKelvin...
If we wanted to integrate this (which I support), we'd likely want to try to create some python objects for this so we can fetch the stats, and then also subscribe so it's updated real time.
Assuming you want this for home assistant (via sdwilsh/hass-truenas), we'll either want to ignore most updates, or strongly encourage folks to setup the recorder integration.
I haven't tried realtime yet. How frequent does the data come in?
The only report that I really want for home assistant that is unavailable from the other services is cpu stats, and I'm not sure which method would be better.
I don't think making recorder a requirement is needed. I do think that if the realtime data is fast, there should be a disclaimer with using it as it could burn through sd cards quickly.
On v2 API at least, certain information is only available via the
stats
service.stats.get_sources
returns a list of sources of datastats.get_sources
Then you can access information about the data by using
stats.get_dataset_info
with args["cputemp-0", "temperature"]
stats.get_dataset_info
Then finally with this info, the data can be retrieved with
stats.get_data
with args[["dataset": "value", "source": "cputemp-0", "type": "temperature"]]
stats.get_data
A lot of the sources are dynamic based on the system, like number of cpu cores (somewhat easy to handle), but then there are pool storage, jails, etc....
Also, I'm not sure how to decipher the units as there is no documentation. The CPU temperatures seem to be in deciKelvin units (is this a common unit for this?) but it is hard to know.
The text was updated successfully, but these errors were encountered: