2010/10/27 maap maap :
> I want you to look this problem from usability side.
> Currently there is no opensource monitoring tools that can easy and without
> any functionality loss handle such data
> representation, you can easely check this by your self , or ask peoples from
> communities.
Well
Dave,
I suggest that our conversation goes at an impasse.
I want you to look this problem from usability side.
Currently there is no opensource monitoring tools that can easy and without any
functionality loss handle such data
representation, you can easely check this by your self , or ask peop
2010/10/20 maap maap :
> I moved to the new kernel and now all sensors are managed by kernel,
> so fan and temperature sensors's indexes been changed
Yes - that's perfectly normal with SNMP.
You cannot assume that index values are necessarily stable across
restarts of the agent. Monitoring appli
Dave,
For example:
I have new motherboard, with lot of sensors, but some of them (assume that all
of em are related to the VOLTAGE_DC
type) are not working because there is no appropriate kernel module.
I moved to the new kernel and now all sensors are managed by kernel,
so fan and temperatu
2010/10/16 maap maap :
> I was so disapointed when discovered that default net-snmp lmsensors
> module uses single index for all sensor's entries,
> even they are placed in different oid tables.
Could you perhaps describe why this is a problem?
You have four separate tables, each of which uses a
Hello Team,
I was so disapointed when discovered that default net-snmp lmsensors module
uses single index for all sensor's entries,
even they are placed in different oid tables.
Example:
iso.3.6.1.4.1.2021.13.16.2.1.1.15 = INTEGER: 15
iso.3.6.1.4.1.2021.13.16.2.1.1.16 = INTEGER: 16
iso.3.6.1.4.
