| 1 |
On Sat, 24 Nov 2012 23:31:30 -0700 |
| 2 |
Joseph <syscon780@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 11/24/12 10:18, Alan McKinnon wrote: |
| 5 |
> >On Fri, 23 Nov 2012 10:44:59 -0700 |
| 6 |
> >Joseph <syscon780@×××××.com> wrote: |
| 7 |
> > |
| 8 |
> >> On 11/23/12 08:40, Alan McKinnon wrote: |
| 9 |
> >> >On Thu, 22 Nov 2012 23:04:17 -0700 |
| 10 |
> >> >Joseph <syscon780@×××××.com> wrote: |
| 11 |
> >> > |
| 12 |
> >> >> I just installed "nagios" but I can not seem to find: check_nrpe |
| 13 |
> >> >> and there is no ebuild: "nagios-nrpe" |
| 14 |
> >> > |
| 15 |
> >> >net-analyzer/nrpe ? |
| 16 |
> >> > |
| 17 |
> >> >-- |
| 18 |
> >> >Alan McKinnon |
| 19 |
> >> >alan.mckinnon@×××××.com |
| 20 |
> >> |
| 21 |
> >> So I think this has to bee installed on the monitoring server and |
| 22 |
> >> the client, isn't it? |
| 23 |
> >> |
| 24 |
> >> How to do you use those plug-ins? I have installed |
| 25 |
> >> "nagios-check_logfiles" plugin and I don't how to use it, is it |
| 26 |
> >> suppose to show up on web-interface? |
| 27 |
> > |
| 28 |
> >I honestly don't know, I don't remember ever installing nrpe on |
| 29 |
> >Gentoo. Everywhere I've used it, it's been on some other distro. |
| 30 |
> > |
| 31 |
> >-- |
| 32 |
> >Alan McKinnon |
| 33 |
> >alan.mckinnon@×××××.com |
| 34 |
> |
| 35 |
> I gave up on this "nagios" too hard to set it up and/or find any |
| 36 |
> decent instructions how to set it up correctly :-) |
| 37 |
> |
| 38 |
|
| 39 |
Nagios itself is quite easy to understand and grasp, but it can be |
| 40 |
fiddly to implement it - mostly because you end up with all kinds of |
| 41 |
little scripts doing useful work and they can all be very different in |
| 42 |
how they expect to be used. |
| 43 |
|
| 44 |
Reading install HOWTO docs for Nagios is a useless activity. You will |
| 45 |
almost always end up finding a doc that describes a different version |
| 46 |
to what you use, and on a different system. I prefer to just understand |
| 47 |
what Nagios does and how it's set up on my machines, then read the |
| 48 |
plugin's code, that tells me how to install and use it. |
| 49 |
|
| 50 |
First thing to understand is what Nagios is, and it's not a monitoring |
| 51 |
tool! That just happens to be the problem people use it to solve. |
| 52 |
Nagios is a state tracking and notification engine. It compares the |
| 53 |
state of something now to the state it was in 5 minutes ago and if |
| 54 |
things changed it sends a notification. |
| 55 |
|
| 56 |
All the monitoring stuff it can do is actually plugins and little |
| 57 |
scripts sitting in various places. To check the state of a ping test, |
| 58 |
Nagios runs a ping test script. That's if Nagios does the test itself, |
| 59 |
you can also have plugins feed information back into Nagios. |
| 60 |
|
| 61 |
Then there's the tests you want to do that Nagios can't see directly, |
| 62 |
like load on a host. You have to log into the host to see that (which |
| 63 |
is dangerous). So there's a daemon running locally on the host called |
| 64 |
nrpe, and Nagios queries this daemon asking it for results. The results |
| 65 |
are the state that Nagios is tracking. |
| 66 |
|
| 67 |
Like I said, script authors like shoving their scripts in any old damn |
| 68 |
place and this is a PITA to sort out when it goes wrong. Rather just |
| 69 |
decide for yourself where things need to go and put them there yourself. |
| 70 |
|
| 71 |
There are so many things Nagios could do much better than it does, but |
| 72 |
the maintainer is highly resistant to adding any features that he |
| 73 |
doesn't use himself. So there are many forks around, why don't you try |
| 74 |
one of those? Some of them are rather well coded. There's many, and |
| 75 |
searching Google for "Nagios forks: will turn up useful projects. |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
-- |
| 81 |
Alan McKinnon |
| 82 |
alan.mckinnon@×××××.com |
Archives