Menu
▾
▴
Re: [opennms-discuss] nsclientpp only collecting one attrib per wpm?
|
From: Tom P. <to...@so...> - 2009-05-29 17:59:10
|
Sound Solutions, Inc.
8400 Highland Dr.
Wausau, WI 54401
Tel: 715-842-7665
Fax: 715-842-7620
We are 99% windows in the 3000+ nodes we monitor....so we tried all
sorts of things.
We saw the same nsclient thing, saw the bug, and shifted gears to
monitor windows machines with snmp. Add the snmp-informant free add-on
and you get all the counters you want to make sure a windows machine is
functioning properly. Opennms will auto-detect everything you need on
the node (given that the snmp community is configured in Windows and
ONMS correctly)...there's pretty much no changes to the 1.6 structure.
It's plug and play man!
Tom P
-----Original Message-----
From: Hans Verbrugge [mailto:han...@gm...]
Sent: Friday, May 29, 2009 7:28 AM
To: General OpenNMS Discussion
Subject: [opennms-discuss] nsclientpp only collecting one attrib per
wpm?
Hi,
I've setup collecting data for nsclientpp 0.3.5.2 to start monitoring
Windows boxes and I'm seeing some odd behaviour.
I'm testing with an XP host, and using OpenNMS 1.6.5
Here's a snipped of nsclient-datacollection-config.xml:
<wpms>
<!-- A group for collecting processor stats.
Check the keyvalue "% Processor Time" - if it's there (should
be) collect this whole group.
Check every recheckInterval milliseconds (3600000 = 1hr) -->
<wpm name="Processor" keyvalue="\Processor(_Total)\% Processor
Time" recheckInterval="3600000">
<!-- Collect these attributes. Name is the name to pass to
NSClient.
Alias is the local name for the RRD file
Type is used to convert values around
maxval/minval are optional-->
<attrib name="\Processor(_Total)\% Processor Time"
alias="cpuProcTime" type="Gauge"/>
<attrib name="\Processor(_Total)\% Interrupt Time"
alias="cpuIntrTime" type="Gauge"/>
<attrib name="\Processor(_Total)\% Privileged Time"
alias="cpuPrivTime" type="Gauge"/>
<attrib name="\Processor(_Total)\% User Time"
alias="cpuUserTime" type="Gauge"/>
</wpm>
<wpm name="System" keyvalue="\System\Processor Queue Length"
recheckInterval="86400000">
<attrib name="\System\Processor Queue Length"
alias="winProcQueueLength" type="Gauge"/>
<attrib name="\System\Processes" alias="winProcesses"
type="Gauge"/>
<attrib name="\System\Threads" alias="winThreads"
type="Gauge"/>
</wpm>
</wpms>
For both entries above, it seems that datacollection is only done for
\Processor(_Total)\% Processor Time
\System\Processor Queue Length
I've got jrb files for those (being updated), but the other attrib
names are not collected.
nsclient reports this:
2009-05-29 14:06:43: debug:.\NSClient++.cpp:947: Injected Performance
Result: ''
2009-05-29 14:06:43: debug:.\NSClientListener.cpp:146: Data: None&8&
\System\Processor Queue Length
2009-05-29 14:06:43: debug:.\NSClientListener.cpp:171: Data: \System
\Processor Queue Length
2009-05-29 14:06:43: debug:.\NSClient++.cpp:910: Injecting:
checkCounter: Counter=\System\Processor Queue Length, nsclient
2009-05-29 14:06:44: debug:.\NSClient++.cpp:946: Injected Result: OK '0'
2009-05-29 14:06:44: debug:.\NSClient++.cpp:947: Injected Performance
Result: ''
Interestingly enough, when I change this wpm :
<wpm name="System" keyvalue="\System\Processor Queue Length"
recheckInterval="86400000">
<attrib name="\System\Processor Queue Length"
alias="winProcQueueLength" type="Gauge"/>
<attrib name="\System\Processes" alias="winProcesses"
type="Gauge"/>
<attrib name="\System\Threads" alias="winThreads"
type="Gauge"/>
</wpm>
to
<wpm name="System" keyvalue="\System\Processor Queue Length"
recheckInterval="86400000">
<attrib name="\System\Processes" alias="winProcesses"
type="Gauge"/>
<attrib name="\System\Processor Queue Length"
alias="winProcQueueLength" type="Gauge"/>
<attrib name="\System\Threads" alias="winThreads"
type="Gauge"/>
</wpm>
Data is being collected for winProcesses and the winProcesses .jrb
file appears.
Seemingly, only the first attrib within a wpm is used, instead of all
elements.
Is this a known bug, or has its behavior changed?
Thanks,
- hans
------------------------------------------------------------------------
------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like
Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-discuss mailing list
To *unsubscribe* or change your subscription options, see the bottom of
this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
--
This message has been scanned for viruses and
dangerous content by Sound Solutions' Avalon Spam Wizard, and is
believed to be clean.
--------------------------------------------------------------------------
Sound Solutions, Inc. - Since 1995
We Appreciate Your Business and Referrals
This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
|