[ehall]

Any more thoughts on using performance counters and splitting the sensors into independent classes?

Thanks

[ehall]

I was able to get WMI queries working from a WBEM-to-WMI gateway, and a WBEM client running on Linux.

CODE

$ wbemcli -nl ei 'http://omega5988/root/WMI:EVEREST_SensorValues'

omega:5988/root/WMI:EVEREST_SensorValues.ID="VCPU"
-ID="VCPU"
-Label="CPU Core"
-Value="1.34"

omega:5988/root/WMI:EVEREST_SensorValues.ID="VP5V"
-ID="VP5V"
-Label="+5 V"
-Value="5.03"

omega:5988/root/WMI:EVEREST_SensorValues.ID="VP12V"
-ID="VP12V"
-Label="+12 V"
-Value="12.38"

omega:5988/root/WMI:EVEREST_SensorValues.ID="FCPU"
-ID="FCPU"
-Label="CPU"
-Value="1187"

omega:5988/root/WMI:EVEREST_SensorValues.ID="TMOBO"
-ID="TMOBO"
-Label="Motherboard"
-Value="38"

omega:5988/root/WMI:EVEREST_SensorValues.ID="VP33V"
-ID="VP33V"
-Label="+3.3 V"
-Value="3.32"

omega:5988/root/WMI:EVEREST_SensorValues.ID="TCPU"
-ID="TCPU"
-Label="CPU"
-Value="49"

I can use this with Cacti and some PHP scripts I think.

This post has been edited by ehall: 31 August 2006 - 02:57 AM

[ehall]

It doesn't appear that any of the negative voltage sensors are being returned

CODE

ID="VAGP",Label="AGP",Value="1.52"
ID="VCPU",Label="CPU Core",Value="1.65"
ID="VP5V",Label="+5 V",Value="5.05"
ID="VP12V",Label="+12 V",Value="11.86"
ID="FCPU",Label="CPU",Value="5192"
ID="TMOBO",Label="Motherboard",Value="43"
ID="VP33V",Label="+3.3 V",Value="3.31"
ID="VBAT",Label="VBAT Battery",Value="3.23"
ID="TCPU",Label="CPU",Value="44"
ID="VDIMM",Label="DIMM",Value="2.69"
ID="FCHA",Label="Chassis",Value="2482"

That machine has a -12V sensor on it, which appears in Everest

[Fiery]

Negative voltages should be there... As long as the values are real

Please copy-paste the full content of the Computer / Sensor page of EVEREST into this topic.


Regards,
Fiery

[Fiery]

Any more thoughts on using performance counters and splitting the sensors into independent classes?

About the independent classes... Can you reformat the output of wbemcli (that you copy-pasted it above) to give us a clear example on how would you imagine the classes thing?


Thanks,
Fiery

[ehall]

[attachmentid=269]

versus

CODE

ID="VAGP",Label="AGP",Value="1.52"
ID="VCPU",Label="CPU Core",Value="1.65"
ID="VP5V",Label="+5 V",Value="5.05"
ID="VP12V",Label="+12 V",Value="11.86"
ID="FCPU",Label="CPU",Value="5192"
ID="TMOBO",Label="Motherboard",Value="43"
ID="VP33V",Label="+3.3 V",Value="3.31"
ID="VBAT",Label="VBAT Battery",Value="3.23"
ID="TCPU",Label="CPU",Value="44"
ID="VDIMM",Label="DIMM",Value="2.69"
ID="FCHA",Label="Chassis",Value="2482"

Attached File(s)

•  beta_sensors.JPG (63.81K)
  Number of downloads: 49

[ehall]

Here's another example of incomplete readings

[attachmentid=270]

versus

CODE

ID="VCPU",Label="CPU Core",Value="1.32"
ID="VP5V",Label="+5 V",Value="5.03"
ID="VP12V",Label="+12 V",Value="12.56"
ID="FCPU",Label="CPU",Value="1189"
ID="TMOBO",Label="Motherboard",Value="39"
ID="VP33V",Label="+3.3 V",Value="3.32"
ID="TCPU",Label="CPU",Value="51"

It's missing two fans, one voltage, and one temp reading

Just to prove it's not a problem with the WBEM-WMI stuff, here's the output from MS WMI Browser, logged in as administrator

[attachmentid=271]

Attached File(s)

•  omega_sensors.JPG (57.33K)
  Number of downloads: 47
•  omega_browser.JPG (35.89K)
  Number of downloads: 50

This post has been edited by ehall: 31 August 2006 - 09:05 PM

[ehall]

About the independent classes... Can you reformat the output of wbemcli (that you copy-pasted it above) to give us a clear example on how would you imagine the classes thing?

I'm basicaly just suggesting that each sensor type have its own class. For example, if they were under /root/cimv2 with typical perfmon names they might be:

/root/cimv2:Win32_PerfPreformattedData_Everest_FanSensors
/root/cimv2:Win32_PerfPreformattedData_Everest_ThermalSensors
/root/cimv2:Win32_PerfPreformattedData_Everest_VoltageSensors

If you don't want to do separate classes, at the very least pleae consider adding a Type property that lets us pre-filter without having to do a regular expression

[Fiery]

Here's another example of incomplete readings

...

It's missing two fans, one voltage, and one temp reading

Just to prove it's not a problem with the WBEM-WMI stuff, here's the output from MS WMI Browser, logged in as administrator

It's normal, since not all values are exposed to 3rd party applications. Only the values you can see in the 2nd post ("A complete list of sensor value IDs and their meaning") are exposed to 3rd party applications.


Regards,
Fiery

[Fiery]

I'm basicaly just suggesting that each sensor type have its own class. For example, if they were under /root/cimv2 with typical perfmon names they might be:

/root/cimv2:Win32_PerfPreformattedData_Everest_FanSensors
/root/cimv2:Win32_PerfPreformattedData_Everest_ThermalSensors
/root/cimv2:Win32_PerfPreformattedData_Everest_VoltageSensors

If you don't want to do separate classes, at the very least pleae consider adding a Type property that lets us pre-filter without having to do a regular expression

Would Type = "F" (or "V", "T") do the job?

[ehall]

It's normal, since not all values are exposed to 3rd party applications.  Only the values you can see in the 2nd post ("A complete list of sensor value IDs and their meaning") are exposed to 3rd party applications.

Uh, can we get that list expanded?

[ehall]

Would Type = "F" (or "V", "T") do the job?

That'd be fine

[Fiery]

Uh, can we get that list expanded?

Expanding it is possible, but we do not plan to add all values EVEREST can detect. That would mean like 100 values


Regards,
Fiery

[Fiery]

BTW, the -12V sensor register of Abit VA-10/11 is used for AGP voltage, so the -12V value displayed by EVEREST is wrong. We'll remove that in the next build.


Regards,
Fiery

[ehall]

Expanding it is possible, but we do not plan to add all values EVEREST can detect.  That would mean like 100 values

How about adding an "external" column to the preferences screen next to the taskbar and OCD columns?

This post has been edited by ehall: 31 August 2006 - 09:33 PM

[Fiery]

That would still mean the list would have 100 entries

We've added the DIMM temperature BTW. Soon we'll post a new beta into this topic.

[Fiery]

Here goes the new beta with the Type WMI entry, the DIMM temperature and the Abit VA-10/11 bug fix.

http://www.lavalys.c...bz3tasxl7kn.zip

Let me know how it works.


Thanks,
Fiery

[ehall]

Here's the D945GTP mobo again. Has the DIMM temp reading, but still missing the other stuff of course:

CODE

ID="TDIMM",Label="DIMM",Type="T",Value="31"
ID="VCPU",Label="CPU Core",Type="V",Value="1.32"
ID="VP5V",Label="+5 V",Type="V",Value="5.00"
ID="VP12V",Label="+12 V",Type="V",Value="12.31"
ID="FCPU",Label="CPU",Type="F",Value="1169"
ID="TMOBO",Label="Motherboard",Type="T",Value="38"
ID="VP33V",Label="+3.3 V",Type="V",Value="3.32"
ID="TCPU",Label="CPU",Type="T",Value="51"

Here's a SOYO board, looks pretty complete too:

CODE

ID="VAGP",Label="AGP",Type="V",Value="1.54"
ID="THDD1",Label="ST380013AS",Type="T",Value="35"
ID="VCPU",Label="CPU Core",Type="V",Value="1.31"
ID="VP5V",Label="+5 V",Type="V",Value="5.05"
ID="VP12V",Label="+12 V",Type="V",Value="11.84"
ID="FCPU",Label="CPU",Type="F",Value="1180"
ID="TMOBO",Label="Motherboard",Type="T",Value="35"
ID="VP33V",Label="+3.3 V",Type="V",Value="3.30"
ID="TCPU",Label="CPU",Type="T",Value="39"
ID="VDIMM",Label="DIMM",Type="V",Value="2.58"
ID="FCHA",Label="Chassis",Type="F",Value="2557"

I can't update the Abit because somebody's using it.

This post has been edited by ehall: 31 August 2006 - 10:12 PM

[ehall]

That would still mean the list would have 100 entries

Curious, what's the problem with that? Too time-consuming to key them all in?

[Fiery]

Curious, what's the problem with that? Too time-consuming to key them all in?

The list would get very long... Hard to follow, hard to manage, and it slows down the hardware monitoring module too.

We're adding more entries only by request, one by one.


Regards,
Fiery