On 15.01.2014 20:23, Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/15/2014 2:05 PM, Michael Friedrich wrote:
On 15.01.2014 17:50, Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have a router that I want to keep an eye on, not so much that
it's up but that the ping latency gets to a certain threshold.
It's a router at our second office in WI whereas I'm in NC.
Is there a way to setup a threshold for that in Icinga2? If so,
how? This particular thorn in my side is primarily why I setup
Icinga in the first place. IIRC, Nagios had a method of doing
it, but the last time I played with Nagios was nearly a decade
ago.
If there's the need of integrating additional plugins, Icinga 2
and Icinga 1.x share the same plugins. In your case you'll probably
want check_ping or check_icmp.
Further details on integrating new plugins are found on the docs in
the section " 2.3 Setting up Check Plugins" at (currently)
http://docs.icinga.org/icinga2/snapshot/
The Icinga Template Library (ITL) already provides a CheckCommand
named "ping4" (details as well on the docs). The CheckCommand
itsself already defines some default macros used as threshold if
your service doesn't set any (like the sample localhost.conf
does).
I know, there are some best practice docs missing, showcasing the
ping use case.
Try the following
object Host "foo" inherits "generic-host" { ... services["ping4"] =
{ templates = [ "generic-service" ]. check_command = "ping4",
macros = { "wrta" = 200, "wpl" = 10, "crta" = 500, "cpl" = 20
"packets" = 3, } } }
You may of course use your own CheckCommand, and freely define the
macros and their names. The ITL just ships the basic templates
everyone needs from our experience in the past years.
As already remarked in the other thread, the documentation requires
your help. If you find anything useful and want to improve it, just
do the following
- fork us on github, clone it locally - cd icinga2 && cd doc - vim
file.md (markdown syntax is easy) - send a pull request - open a
new issue at https://dev.icinga.org in the Icinga 2 section
That way everyone may contribute and speed up the way to the final
version :)
Any help would be appreciated. So far, I'm absolutely loving
Icinga2. It's just fantastic.
:-)
I was hoping that this would be an option with the existing ping4
service. Your config is exactly what I needed.
Now, I have two more questions.
Where is the services like ping4 defined? I can't seem to find them.
(But then it's probably under my nose.)
Look into my example. The host contains the services array containing an
implicit service declaration at "ping4". It inherits from the
"generic-service" template, and set the check_command attribute in
reference to the "ping4" CheckCommand. If it's not that obvious, take
the following example.
object Host "foo" inherits "generic-host" {
...
services["bumsti"] = {
templates = [ "generic-service" ].
check_command = "ping4",
macros = {
"wrta" = 200,
"wpl" = 10,
"crta" = 500,
"cpl" = 20
"packets" = 3,
}
}
}
That will implicitely create a host object called "foo", and a service
object with the internal name "foo!bumsti". You won't recognize that
since you're advised to use the display_name attribute as well.
There's a short mention about inline services on the host object docs,
but that'll be better explained too. https://dev.icinga.org/issues/5477
Also, I can't seem to get notifications setup correctly. I'm wondering
if there is an additional step that's not listed in the online docs;
sendmail configuration or something?
Hmmm as far as i know the sample notification command should be fixed,
using the provided script instead. And then, the mail binary and your
preferred MTA should work as well, yep.
As far as contributing goes, I'll be happy too. I really need to get
much more familiar with it before I start offering changes. I have
spent the last 5 years semi-retired (in my late 30s no less), having 6
surgeries to repair badly arthritic joints, and I've been back in full
time IT less than 6 months. Pulling up all the old IT knowledge is
getting easier, but I'm not even close to being able to do what I
could back when I worked for NOAA.
But, I'm making plenty of notes, and hopefully they will be of some
use when I'm happy with them.
We're always looking for motivated community members to join the team.
It's not a requirement to work 1h a day on Icinga, but to keep it going
and have fun while it lasts. Or while you learn more from an open source
project than the best studies would ever teach you.
There's not much to do, but apply for being an Icinga padawan ;-)
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
