Figured this one out. Just had to change this
export MK_LIBDIR="/usr/lib/check_mk_agent"
to
export MK_LIBDIR="/usr/lib/observium_agent"
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
From: observium [observium-bounces@observium.org] on behalf of Tom Taylor [taylor@themill.com]
Sent: Tuesday, February 11, 2014 11:04 AM
To: Observium Network Observation System
Subject: Re: [Observium] NFS application monitor
Right, so I've followed all the steps to get the agent working but no bueno.
If I run this manually, it doesn't look like it's picking up my additional NFS module:/usr/bin/observium_agent
cd /usr/lib/observium_agent/local
[root@bugsy local]# ls
nfs
Running the NFS agent manually works though
[root@bugsy local]# ./nfs
<<<app-nfs>>>
net 0 0 0 0
rpc 2097021494 55 2097119627
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 0 1490695718 39587573 67447242 272522805 3298218 57271127 128942617 659890 165341 35452 5 406761 51002 652196 16244 38710 33760696 1055322 24 12 0
proc4 47 0 2330 4670 1 10 8 0 0 8 0 4 25959 1 1 0 0 0 99848 43 84753 1 82159 0 0 0 1670 3 127108 0 10 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
I can telenet into the client on port 6556 (The default in xinet.d/observium_agent) and it pulls a bunch of info but not the NFS stats.
Any ideas?
-TT
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
From: observium [observium-bounces@observium.org] on behalf of Tom Taylor [taylor@themill.com]
Sent: Monday, February 10, 2014 5:45 PM
To: Observium Network Observation System
Subject: Re: [Observium] NFS application monitor
Ah great, all working now.
Thanks for this, I now too understand how the agent works :)
-TT
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
From: Tom Laermans <tom.laermans@powersource.cx>
Reply-To: Observium Network Observation System <observium@observium.org>
Date: Monday, February 10, 2014 at 3:53 PM
To: Observium Network Observation System <observium@observium.org>
Subject: Re: [Observium] NFS application monitor
Hi Tom,
For most of the agent scripts, you usually place the script from observium's scripts/agent-local folder into the "local" folder of the Observium agent; try running it on that host and see if it returns data. Use the "search" function on the wiki, some of the agent scripts do have (some) documentation and have some dependencies.
Note: NFS is somewhat of a difficult thing, as it's parsing a file in /proc which changes in between kernels! Touchy subject... :-)
Tom
On 10/02/2014 22:32, Tom Taylor wrote:
Howdy,
Does anyone have any info on how to set up the NFS application monitoring? I've taken a read through of the install docs and there's no mention of the NFS monitor.
Any ideas ?
-TT
Tom Taylor
Head of Engineering, Chicago
T +1 312 605 8900
The Mill 54 West Hubbard Street, Suite 502, Chicago, IL, 60654
themill.com | themillblog.com | @millchannel | facebook.com/millchannel
_______________________________________________ observium mailing list observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium