[collectd] Fwd: adsl monitoring via snmp
Hi all, I have recently obtained a new (for me) adsl terminal adapter - and would rather like to keep an eye on it. The plan is to use snmp via collectd. Unfortunately, it isn't quite working... Can anyone give me a hand? Doing snmpwalk, I get (amongst other things) this: IF-MIB::ifInOctets.1 = Counter32: 4192850 IF-MIB::ifInOctets.2 = Counter32: 0 IF-MIB::ifInOctets.3 = Counter32: 0 IF-MIB::ifInOctets.4 = Counter32: 63017231 IF-MIB::ifInOctets.5 = Counter32: 1000 IF-MIB::ifOutOctets.1 = Counter32: 58867993 IF-MIB::ifOutOctets.2 = Counter32: 0 IF-MIB::ifOutOctets.3 = Counter32: 0 IF-MIB::ifOutOctets.4 = Counter32: 2500412 IF-MIB::ifOutOctets.5 = Counter32: 1000 looking at the recipe at https://collectd.org/wiki/index.php/Plugins:SNMP/Config I attempted to use this: Plugin snmp Data if Type if_octets Table true Instance IF-MIB::ifDescr Values IF-MIB::ifInOctets IF-MIB::ifOutOctets /Data Host gateway.local Address 192.168.1.1 Version 1 Community public Collect if /Host /Plugin Problem: This isn't collecting complete, reliable data, but instead gives the following error: [2013-05-17 20:05:56] [notice] uc_update: Value too old: name = gateway.local/snmp/if_octets; value time = 1368817556.568; last cache update = 1368817556.568; [2013-05-17 20:05:56] [info] Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Why? and, more importantly, how do I fix this? From the FAQ, this is down to a misconfiguration of the SNMP plugin. Indeed, removing the 'Instance' line fixes the problem - but introduces another: I go from monitoring adsl (WAN), eth (LAN) VLAN traffic to monitoring if_octets 1 through 5 *and* wan, lan vlan., of which the first 5 are always empty! (which confuses me, since I only have 5 oids). What gives? Thanks, Phil ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Onewire Plugin
Hi All, Thanks Tomas - all is working. I'm afraid I didn't go with your patch in the end (mainly because I lost the ability to automatically read a sensor without specifically including the path location in the configuration). However, it pointed me in a direction which enabled me to cobble together a working solution. Apart from a very minor patch to the onewire module, most of the time was spent on OWFS. i really didn't like the way this made the readings available (under a sub-directory). Reading the comments, I suspect that this is a OWFS design problem, rather than collectd. If ever I get the time, I might look into this a bit more. Since i am looking at a large system, hints tips prior to this welcomed. Best regards, Phil On 13 January 2012 17:36, Phil White manx@googlemail.com wrote: Hi Tomas, Thanks - I'll have a look over the weekend, and let you know how I get on. Cheers On 13 January 2012 16:52, Tomas tomasa...@googlemail.com wrote: Hi Phil, you could use my patch - see http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html This would solve your problem with device family 28 (had the same problem). For the other device with 7E you can use the other option which offers the patch - to use direct accss by specifying the whole OWFS path (also documented in the patch). Or just use it as an inspiration :-) Best regards, Tomas On 13/01/2012 14:55, Phil White wrote: Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing listcollectd@verplant.orghttp://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Onewire Plugin
Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Onewire Plugin
Hi Tomas, Thanks - I'll have a look over the weekend, and let you know how I get on. Cheers On 13 January 2012 16:52, Tomas tomasa...@googlemail.com wrote: Hi Phil, you could use my patch - see http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html This would solve your problem with device family 28 (had the same problem). For the other device with 7E you can use the other option which offers the patch - to use direct accss by specifying the whole OWFS path (also documented in the patch). Or just use it as an inspiration :-) Best regards, Tomas On 13/01/2012 14:55, Phil White wrote: Hello all, Long ago, I looked at collectd and 1-wire monitoring, and never progressed because I had problems with owfs, and because of the plugin's 'experimental' status (though I do use collectd for other monitoring). I revisited the issue the other day, and still can't get things to work (though for different reasons). I have DS18B20 as my temperature sensors, rather than the DS18S20 that the plugin appears to recognise. These report themselves as a device with the prefix '28', rather than 10 - therefore collectd does not record data from these sensors. Now, I'd rather like to have a play with the plugin, and attempt to get this working. Rather than just submit a request, I'd rather like to get my hands dirty, and fix it myself. Just because I have never done any coding in C really shouldn't stop me, should it?! Another reason being that I also have a device prefix '7E', which is somewhat different, and I'd also like to see this one recognised. Therefore, can someone offer some 'beginners tips' as to how I'm going to start on the '28' issue - advice info? Which files, and what I need to do in order not to break anything? Many thanks, Phil ___ collectd mailing listcollectd@verplant.orghttp://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
