<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>An It-Slave in the digital saltmine &#187; op5 Monitor</title>
	<atom:link href="http://www.it-slav.net/blogs/category/op5-monitor/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.it-slav.net/blogs</link>
	<description>Another Blog from a Geek that has no life</description>
	<lastBuildDate>Fri, 02 Jul 2010 07:33:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Splunk are not open</title>
		<link>http://www.it-slav.net/blogs/2010/05/25/splunk-are-not-open/</link>
		<comments>http://www.it-slav.net/blogs/2010/05/25/splunk-are-not-open/#comments</comments>
		<pubDate>Tue, 25 May 2010 14:02:32 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[splunk]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1806</guid>
		<description><![CDATA[&#160;
I have registred me to attend&#160;the open Splunk event in Stockholm. Within 24 hours I&#160;got an email telling that they do not want competitors at the event and would like to discuss the purpose of me attending.
I&#160;called the Splunk representative and told him that op5 thinks Splunk is a competitor in some cases and in [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p>I have registred me to attend&nbsp;the open <a href="http://www.splunk.com">Splunk</a> <a href="http://www.splunk.com/goto/SplunkLive_Stockholm_0510">event in Stockholm</a>. Within 24 hours I&nbsp;got an email telling that they do not want competitors at the event and would like to discuss the purpose of me attending.</p>
<p>I&nbsp;called the Splunk representative and told him that op5 thinks Splunk is a competitor in some cases and in some cases we have products that run in parallel at customer sites. We want to integrate <a href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a> with Splunk because we have got the question a couple of times from customers and potential customers. My intention of attending the meeting is to get a better understanding of Splunk so op5 can integrate our products, so our customers get the products that suits them best. If Splunk wants to be part of the integration, the better.</p>
<p>The Splunk representative still do not want me to attend. At Splunk they will discuss this matter internally but so far, this is their view.</p>
<p>&nbsp;</p>
<p>I&nbsp;would really like to make a parallel with another op5 competitor, W&uuml;rth, at their <a href="http://www.wuerth-phoenix.com/en/company/event/the-agenda/">event</a> they invited op5 as key speaker and I&nbsp;really recommend Splunk to reconsider their decision.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/05/25/splunk-are-not-open/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Android app for Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2010/05/01/android-app-for-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2010/05/01/android-app-for-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Sat, 01 May 2010 13:30:56 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[NagMonDroid]]></category>
		<category><![CDATA[Nagroid]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1764</guid>
		<description><![CDATA[&#160;
With my new and fancy HTC Desire I wanted to look at my Nagios or op5 Monitor status. I&#160;have found two apps Nagroid and NagMonDroid.
&#160;
NagMonDroid did I&#160;not get working, probably because op5 Monitor only uses https as protocol.
&#160;
Nagroid works like a charm:

&#160;
The configuration is rather straightforward:

]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p>With my new and fancy HTC Desire I wanted to look at my <a href="http://www.nagios.org">Nagios</a> or <a href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a> status. I&nbsp;have found two apps <a href="http://www.kiu.weite-welt.com/de.schoar.android//nagroid/help/">Nagroid</a> and <a href="http://www.simonmclaughlin.co.uk/page/Android_Apps/">NagMonDroid</a>.</p>
<p>&nbsp;<span id="more-1764"></span></p>
<p>NagMonDroid did I&nbsp;not get working, probably because op5 Monitor only uses https as protocol.</p>
<p>&nbsp;</p>
<p>Nagroid works like a charm:</p>
<p><a href="http://www.it-slav.net/blogs/wp-content/uploads/2010/05/nagroid.png"><img width="480" height="800" src="http://www.it-slav.net/blogs/wp-content/uploads/2010/05/nagroid.png" alt="" title="nagroid" class="aligncenter size-full wp-image-1765" /></a></p>
<p>&nbsp;</p>
<p>The configuration is rather straightforward:</p>
<p><a href="http://www.it-slav.net/blogs/wp-content/uploads/2010/05/nagroid-settings.png"><img width="480" height="800" class="aligncenter size-full wp-image-1768" title="nagroid-settings" alt="" src="http://www.it-slav.net/blogs/wp-content/uploads/2010/05/nagroid-settings.png" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/05/01/android-app-for-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Finally it has arrived, my HTC Desire</title>
		<link>http://www.it-slav.net/blogs/2010/04/30/finally-it-has-arrived-my-htc-desire/</link>
		<comments>http://www.it-slav.net/blogs/2010/04/30/finally-it-has-arrived-my-htc-desire/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 18:09:22 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Fon]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[asterisk]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[htc desire]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1740</guid>
		<description><![CDATA[After waiting for several weeks, my new phone, a HTC Desire has finally arrived. I have been a heavy cellphone user since started working as a Tivoli consultant in -98. I bought my first cellphone -94 and have had several so called smart phones both from Nokia and Ericsson.
&#160;
For the first time I felt that [...]]]></description>
			<content:encoded><![CDATA[<p>After waiting for several weeks, my new phone, a HTC Desire has finally arrived. I have been a heavy cellphone user since started working as a Tivoli consultant in -98. I bought my first cellphone -94 and have had several so called smart phones both from Nokia and Ericsson.</p>
<p>&nbsp;</p>
<p>For the first time I felt that this is more than a phone, for the first time calender integration works, for the first time I can use the builtin GPS, for the first time accessing the web with a phone works, for the first time downloaded software really works.</p>
<p>&nbsp;<span id="more-1740"></span></p>
<p>&nbsp;</p>
<p>My favorite apps so far is:</p>
<ul>
<li>Nagroid, to be able to view my <a href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a> status</li>
<li>FONMaps, find hotspots for LaFoneras</li>
<li>Car Cast, listen and download podcasts</li>
<li>MapDroid, to use preloaded OpenStreetmaps and GPS without using any bandwidth. Perfect when abroad because of the crazy price of data roaming outside Sweden.</li>
<li>HTC&nbsp;Facebook, read and post on facebook</li>
<li>FON&nbsp;Access, automatically connect to FON&nbsp;hotspots when traveling.</li>
<li>GPS Logger, logg tracks in gpx format that almost any GPS software understand</li>
<li>Sipdroid, to connect to my Asterisk PBX using 3G or WiFi</li>
</ul>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Of&nbsp; cource the device is not perfect, I miss:</p>
<ul>
<li>The phone must be &#8216;rooted&#8217; to be real useful, why? Open the phone so the community and others can develop apps that are real useful. Vendor lock-in always sucks.</li>
<li>IPSec VPN so I&nbsp;can connect to my IPSec based OpenBSD firewall. The IPSec implementation in the phone sucks.</li>
<li>OpenVPN, there exists OpenVPN&nbsp;apps but to use the the phone must be &#8216;rooted&#8217;</li>
<li>Bluetooth modem, it is not possible to use the phone as a modem using bluetooth</li>
<li>Screenshots, the phone must be rooted or using the SDK to take screenshoots. Why?</li>
</ul>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>I really hope that Google and/or HTC understand and use the power of the community to make the Android even more succesfull by open it even more.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/04/30/finally-it-has-arrived-my-htc-desire/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Monitor HP Proliant with Nagios or Op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2010/03/02/monitor-hp-proliant-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2010/03/02/monitor-hp-proliant-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 20:38:52 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[HP SIM]]></category>
		<category><![CDATA[Insight Manager]]></category>
		<category><![CDATA[SIM]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1644</guid>
		<description><![CDATA[&#160;
Background
It is always a good idea to monitor the server hardware, in many cases the root cause of the probblem is hardware related like: a fan stops and the temperature gets to high, dust in the machine makes it to hot, disks that fails, memory corruption and so on.&#160; This article will describe howto enable [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<h2>Background</h2>
<p>It is always a good idea to monitor the server hardware, in many cases the root cause of the probblem is hardware related like: a fan stops and the temperature gets to high, dust in the machine makes it to hot, disks that fails, memory corruption and so on.&nbsp; This article will describe howto enable hardware monitoring on a HP&nbsp;Proliant running CentOS Linux and then howto collect the data with Nagios or op5 Monitor. The procedure is the same with RedHat Enterprise Linux and similiar with Suse Enterprise server.</p>
<p>The HP&nbsp;manuals and information is bloated with irrelevant information and I&nbsp;had to struggle several hours, ask collegues to get it running. I&nbsp;hope this blog article will help others to get monitoring of HP Proliant using HP Insight Manager easier to setup.</p>
<h2>&nbsp;<span id="more-1644"></span></h2>
<p>&nbsp;</p>
<h2>Installing the software on the target system</h2>
<p>You need two packages from HP and can be downloaded from <a href="http://www.hp.com">hp.com</a> under &quot;Support &amp; Drivers&quot;. Search your hardware plattform and correct operating system:</p>
<ul>
<li>ProLiant Support Pack for Red Hat Enterprise Linux 5 (i686)&nbsp; The latest Proliant Support Package 2010-03-02 name is psp-8.25.rhel5.i686.en.tar.gz</li>
<li>HP System Health Application and Insight Management Agents for Red Hat Enterprise Linux 5 (x86). The latest name is hpasm-8.0.0-173.rhel5.i386.rpm</li>
</ul>
<p>&nbsp;</p>
<p>Install kernel source code and rpm tools:</p>
<pre>
# yum install kernel-devel rpm-build rpm-devel
 </pre>
<p>&nbsp;</p>
<p>Proliant Support Package is not supported on CentOS so you have to let the installer think it is a RedHat system. If you have a RHEL&nbsp;system skip the next steps.</p>
<pre>
# cp /etc/redhat-release /etc/redhat-release.backup

# echo &quot;Red Hat Enterprise Linux Server release 5.4 (Tikanga)&quot;&gt;/etc/redhat-release</pre>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Untar the Proliant Support Package</p>
<pre>
 # tar xzvf psp-8.25.rhel5.i686.en.tar.gz</pre>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Install the  Proliant Support Package</p>
<pre>
# cd compaq/csp/linux/

# ./install825.sh</pre>
<p>alot of text appears and some questions, answer them.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Install HP System Health Application and Insight Management Agents, and for some stupid reason it is in conflict with some other packages just installed. I solved it in a dirty way:</p>
<pre>
# rpm -i --force  --replacefiles --nodeps hpasm-8.0.0-173.rhel5.i386.rpm</pre>
<p>Configure by running:</p>
<pre>
# hpa/etc/init.d/hpasm configure</pre>
<p>and answer the questions.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Do not forget to restore /etc/redhat-release</p>
<pre>
# cp /etc/redhat-release.backup /etc/redhat-release</pre>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>I&nbsp;did modify my /etc/snmp/snmp.conf to:</p>
<pre>
dlmod cmaX /usr/lib/libcmaX.so
rocommunity public
trapsink 10.1.1.20
syscontact peter@it-slav.net
syslocation PDC, Peters DataCenter</pre>
<p>&nbsp;</p>
<p>To test that you have installation and configuration work, run a snmpwalk from your Nagios or op5 Monitor host:</p>
<pre>
# snmpwalk -c public -v1  &lt;ip-adress of your proliant box&gt; 1.3.6.1.4.1.232

SNMPv2-SMI::enterprises.232.1.1.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.232.1.1.2.0 = INTEGER: 23
SNMPv2-SMI::enterprises.232.1.1.3.0 = INTEGER: 2
SNMPv2-SMI::enterprises.232.1.2.1.4.1.0 = INTEGER: 30
SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.2.1 = STRING: &quot;Compaq Standard Equipment Agent for Linux&quot;
SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.3.1 = &quot;&quot;
SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.4.1 = Hex-STRING: 00 00 00 00 00 00 00
SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.5.1 = STRING: &quot;To gather Standard Equipment data for Linux.&quot;

...
 </pre>
<h2>&nbsp;</h2>
<h2>Install check_hpasm on the Nagios or op5 Monitor host</h2>
<p>The <a href="http://labs.consol.de/lang/en/nagios/check_hpasm/">check_hpasm</a> can be downloaded from <a href="http://labs.consol.de/">Console Labs</a>.</p>
<p>Unpack the tarball</p>
<pre>
# tar xzvf check_hpasm-4.1.2.tar.gz</pre>
<p>&nbsp;</p>
<pre>
Configure and compile

# ./configure --prefix=/opt/plugins/custom/hp-insight --with-nagios-user=monitor --with-nagios-group=users --enable-perfdata

...

# make

...

# make install</pre>
<p>&nbsp;</p>
<p>Test</p>
<pre>
# /opt/plugins/custom/hp-insight/libexec/check_hpasm -H  -C public

OK - System: 'proliant dl360 g3', S/N: '7J31LMW6N01D', ROM: 'P31 01/28/2004', hardware working fine, da: 1 logical drives, 1 physical drives | fan_1=50% fan_2=50% temp_1_cpu=16;50;50 temp_2_cpu=15;65;65 temp_3_ioBoard=21;56;56 temp_4_cpu=20;65;65
</pre>
<p>Congratulations your plugin and hw monitoring works!</p>
<p>&nbsp;</p>
<h2>Configure Nagios or op5 Monitor<br />
&nbsp;</h2>
<p>checkcommands.cfg</p>
<pre>
# command 'check_hpasm'
define command{
    command_name                   check_hpasm
    command_line                   $USER1$/custom/libexec/check_hpasm -H $HOSTADDRESS$ -C $ARG1$
    }</pre>
<p>&nbsp;</p>
<p>services.cfg</p>
<pre>
# service 'Insight Manager'
define service{
    use                            default-service
    host_name                      humpa
    service_description            Insight Manager
    check_command                  check_hpasm!public
    contact_groups                 call_it-slav,it-slav_jabber,it-slav_mail
    }</pre>
<h2>&nbsp;</h2>
<p>Screenshoot, using ninja</p>
<p><a href="http://www.it-slav.net/blogs/wp-content/uploads/2010/03/hpinsightmgr.png"><img width="1242" height="182" src="http://www.it-slav.net/blogs/wp-content/uploads/2010/03/hpinsightmgr.png" alt="" title="hpinsightmgr" class="aligncenter size-full wp-image-1658" /></a></p>
<p>&nbsp;</p>
<h2>&nbsp;Useful links</h2>
<ul>
<li><a href="http://www.op5.com">op5</a>, a systems and network management company</li>
<li><a href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a>, an enterpise monitor system based on Nagios</li>
<li><a href="http://www.op5.org/community/projects/ninja">Ninja</a>, Nagios is now just awesome</li>
<li><a href="http://www.nagios.org">Nagios</a>, enterprise monitoring based on opensource</li>
<li><a href="http://welcome.hp.com/country/us/en/support.html">Hp support &amp; drivers</a>, a place to start looking for the HP software used in this article</li>
</ul>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/03/02/monitor-hp-proliant-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>op5 Monitor 5.0 Beta</title>
		<link>http://www.it-slav.net/blogs/2010/02/26/op5-monitor-5-0-beta/</link>
		<comments>http://www.it-slav.net/blogs/2010/02/26/op5-monitor-5-0-beta/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 19:58:49 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1626</guid>
		<description><![CDATA[The release of the next generation Open Source Network Monitoring Software is only weeks away with the release of op5 Monitor 5. Here you can download a Beta version of the sofware intended for testing och evaluation or try it at a live demo.

op5 Monitor Beta, virtual image in ovf format
Try op5 Monitor Beta

The op5 [...]]]></description>
			<content:encoded><![CDATA[<p>The release of the next generation Open Source Network Monitoring Software is only weeks away with the release of op5 Monitor 5. Here you can download a Beta version of the sofware intended for testing och evaluation or try it at a live demo.</p>
<ul>
<li><a href="http://www.op5.com/op5/products/network-monitor/download-50-beta#">op5 Monitor Beta, virtual image in ovf format</a></li>
<li><a href="https://beta.op5.com/ninja">Try op5 Monitor Beta</a></li>
</ul>
<p>The op5 Monitor Beta use <a href="http://www.op5.org/community/projects/ninja">Ninja</a> as GUI and <a href="http://www.op5.org/community/projects/merlin">Merlin</a> as a databasebackend.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/02/26/op5-monitor-5-0-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Merlin and Ninja roadmap</title>
		<link>http://www.it-slav.net/blogs/2010/02/17/merlin-and-ninja-roadmap/</link>
		<comments>http://www.it-slav.net/blogs/2010/02/17/merlin-and-ninja-roadmap/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 12:24:38 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1598</guid>
		<description><![CDATA[An email sent to op5-users from op5s CTO, Peter &#214;stlin.
&#8211;cut&#8211;
Hi All,
The op5 devel team has been kind of quiet on the list lately. The
reason for this is that we have been working very hard to complete the
next release of Merlin and Ninja. The result of this will be the
release of op5 Monitor 5.0 scheduled for [...]]]></description>
			<content:encoded><![CDATA[<p>An email sent to op5-users from op5s CTO, Peter &Ouml;stlin.</p>
<p>&#8211;cut&#8211;</p>
<address>Hi All,</address>
<address>The op5 devel team has been kind of quiet on the list lately. The<br />
reason for this is that we have been working very hard to complete the<br />
next release of Merlin and Ninja. The result of this will be the<br />
release of op5 Monitor 5.0 scheduled for public availability April 13.<br />
In this release Merlin and Ninja will be version 1.0 which mean all<br />
our customers and users will benefit from production quality tools.<br />
<span id="more-1598"></span><br />
Compared to the currently released versions, Merlin v0.6.6 and Ninja<br />
v0.3.6, the release include for example:</address>
<ul>
<li>Implementation of the missing Nagios cgi&#8217;s. (showlog, history,trends, notifications etc)</li>
<li>Include Avail/SLA reports in Ninja&nbsp; (Avail reports are an improved version of the Nagios avail reports and SLA is a new report type)</li>
<li>Lots of bugfixes</li>
</ul>
<address>&nbsp;</address>
<address>&nbsp;</address>
<address>The schedule for the release of op5 Monitor 5.0 (as well as Merlin 1.0<br />
and Ninja 1.0) is as follow:</address>
<address>2010-02-26 &#8211; Beta release<br />
2010-03-12 &#8211; Release candidate 1<br />
2010-03-26 &#8211; Stable release is tagged and build<br />
2010-04-13 &#8211; op5 Monitor 5.0 General Availability</address>
<address>&nbsp;</address>
<address>&nbsp;</address>
<address>As always, this is a plan and might change slightly. There might be<br />
need for extra beta/rc builds for example. We will keep you posted<br />
regarding the progress.</address>
<address>Cheers,<br />
Peter &Ouml;stlin<br />
op5 AB</address>
<p>&#8211;cut&#8211;</p>
<h2>Links</h2>
<ul>
<li><a href="http://www.op5.org/community/projects/ninja">Ninja</a>, Nagios Is Now Just Awesome</li>
<li><a href="http://www.op5.org/community/projects/merlin">Merlin</a>, Module for Endless Redundacy and Loadbalancing In Nagios</li>
<li><a href="http://www.op5.com">op5</a>, a company with enterprise network- and systems management based on OpenSource.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/02/17/merlin-and-ninja-roadmap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Monitoring BizTalk with Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2010/02/05/monitoring-biztalk-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2010/02/05/monitoring-biztalk-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 19:39:55 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[Biztalk]]></category>
		<category><![CDATA[biztalk monirtoring]]></category>
		<category><![CDATA[biztalk nagios]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1581</guid>
		<description><![CDATA[&#160;
Background
At op5 we often run into BizTalk at customer sites as a business critical application. We have done an investigation and come up with a plugin&#160; to monitor BizTalk.
To fully understand this document BizTalk knowledge is necessary.

&#160;
Solution
op5 has developed a plugin that can monitor the following at a BizTalk server:

Recieve locations &#8211; Verify that they [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<h2>Background</h2>
<p>At op5 we often run into <a href="http://en.wikipedia.org/wiki/Biztalk" target="_blank">BizTalk</a> at customer sites as a business critical application. We have done an investigation and come up with a plugin&nbsp; to monitor BizTalk.</p>
<p>To fully understand this document BizTalk knowledge is necessary.</p>
<p><span id="more-1581"></span></p>
<p>&nbsp;</p>
<h2>Solution</h2>
<p>op5 has developed a plugin that can monitor the following at a BizTalk server:</p>
<ul>
<li>Recieve locations &#8211; Verify that they are enabled.</li>
<li>Send Ports &#8211; Verify that they are in Started state</li>
<li>Group Overview &#8211; Catch messages in the message queue that are in state Suspended. The different type of messages are:
<ul>
<li>Dehydrated</li>
<li>Suspended</li>
<li>Queue</li>
</ul>
</li>
</ul>
<p>The plugin license is GPLv3 so it is free for any one to use and enhance.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h2>Links</h2>
<ul>
<li><a href="http://git.op5.org/git/?p=nagios/op5plugins.git;a=blob;f=check_biztalk.pl">check_biztalk</a> the plugin that monitors BizTalk</li>
<li><a href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a> Monitor solution based on Nagios</li>
<li><a href="http://www.nagios.org">Nagios</a> free enterprise monitor software</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2010/02/05/monitoring-biztalk-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keep track of unused switch ports with Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/11/24/keep-track-of-unused-switch-ports-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/11/24/keep-track-of-unused-switch-ports-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 10:12:02 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[unused switch ports]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1485</guid>
		<description><![CDATA[Background
I&#160;was reading the Swedish computer magazine, Tech World. There was an article about an appliance solution that could give a report about unused switch ports. The box PortIQ from Infoblox costs approximatly 10.000 Euro.
op5 has developed this feature at a customer site and is included with op5 Monitor, op5 has published the code as opensource.
This [...]]]></description>
			<content:encoded><![CDATA[<h2>Background</h2>
<p>I&nbsp;was reading the Swedish computer magazine, <a target="_blank" href="http://techworld.idg.se/">Tech World</a>. There was an article about an appliance solution that could give a report about unused switch ports. The box <a target="_blank" href="http://www.infoblox.com/products/portiq-appliances.cfm">PortIQ</a> from Infoblox costs approximatly 10.000 Euro.</p>
<p><a target="_blank" href="http://www.op5.com">op5</a> has developed this feature at a customer site and is included with <a target="_blank" href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a>, op5 has published the code as <a target="_blank" href="http://git.op5.org/git/">opensource</a>.</p>
<p>This guide will describe howto get it running in op5 Monitor. op5 Monitor is vanilla Nagios with some addons so it should be no problem to follow this guide in a Nagios environment</p>
<p>&nbsp;</p>
<p><span id="more-1485"></span>&nbsp;</p>
<h2>Installation</h2>
<p>1. Update your op5 Monitor or <a href="http://git.op5.org/git/?p=nagios/op5plugins.git;a=tree;f=check_portstatus;h=120bf07e50d72c1a1beb0a8963cd45a5341e7727;hb=5759746d3bcd457d344c21d9befa5611515a9acb" target="_blank">download</a> the plugin and report script.</p>
<p>&nbsp;</p>
<p>2. Create metadata for check_portstatus as $USER1$/check_portstatus -H  $HOSTADDRESS$</p>
<p>in checkcommands.cfg:</p>
<p><code># command 'check_portstatus'<br />
define command{<br />
&nbsp;&nbsp;&nbsp; command_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_portstatus<br />
&nbsp;&nbsp;&nbsp; command_line&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $USER1$/check_portstatus -H $HOSTADDRESS$<br />
&nbsp;&nbsp;&nbsp; }</code><br />
&nbsp;</p>
<p>3. mkdir /var/spool/check_portstatus</p>
<p>&nbsp;</p>
<p>4. chown monitor:apache /var/spool/check_portstatus</p>
<p>&nbsp;</p>
<p>5. cp /opt/monitor/op5/portstatus/portstatus.php  /var/www/html/portstatus.php</p>
<p>&nbsp;</p>
<p>6. Define your service i.e. services.cfg:</p>
<p><code># service 'Portstatus'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gw<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Portstatus<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_portstatus<br />
&nbsp;&nbsp;&nbsp; }</code><br />
&nbsp;</p>
<h2>&nbsp;</h2>
<h2>The result</h2>
<p>The screenshot below shows a Cisco switch with alot of unused ports.</p>
<p><img width="692" height="713" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/11/portstatus1.png" alt="portstatus" title="portstatus" class="aligncenter size-full wp-image-1488" /></p>
<p>&nbsp;</p>
<h2>&nbsp;</h2>
<h2>Conclusions</h2>
<p>This article shows how easy it is to modify Nagios and other opensource tools to give you what you want. Do not hesitate to contact <a href="javascript:location.href='mailto:'+String.fromCharCode(112,101,116,101,114,64,105,116,45,115,108,97,118,46,110,101,116)+'?'">me</a> or <a target="_blank" href="http://www.op5.com">op5</a> to help you enhance you Nagios or op5 installation.</p>
<h2>&nbsp;</h2>
<h2>Links</h2>
<ul>
<li><a target="_blank" href="http://www.op5.com">op5</a></li>
<li><a target="_blank" href="http://www.op5.com/op5/products/network-monitor">op5 Monitor</a></li>
<li><a target="_blank" href="http://www.nagios.org">Nagios</a></li>
<li><a target="_blank" href="http://www.infoblox.com/products/portiq-appliances.cfm">PortIQ</a> appliance box from Infoblox</li>
<li><a target="_blank" href="http://techworld.idg.se/">Tech world</a></li>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/11/24/keep-track-of-unused-switch-ports-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Rule engine integration with Nagios using NodeBrain</title>
		<link>http://www.it-slav.net/blogs/2009/10/22/rule-engine-integration-with-nagios-using-nodebrain/</link>
		<comments>http://www.it-slav.net/blogs/2009/10/22/rule-engine-integration-with-nagios-using-nodebrain/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 18:40:59 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[nagios rule engine]]></category>
		<category><![CDATA[nodebrain]]></category>
		<category><![CDATA[Rule engine]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1423</guid>
		<description><![CDATA[Background
This article will describe how easy it is to integrate other tools to Nagios or op5 Monitor. I&#160;will use an example with a webshop where a business view of how the webshop is doing is implemented by using a GPL&#8217;d rule engine, NodeBrain. I have in an earlier article described the ruleset for this implementation [...]]]></description>
			<content:encoded><![CDATA[<h2>Background</h2>
<p>This article will describe how easy it is to integrate other tools to <a target="_blank" href="http://www.nagios.org">Nagios</a> or <a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a>. I&nbsp;will use an example with a webshop where a business view of how the webshop is doing is implemented by using a GPL&#8217;d rule engine, NodeBrain. I have in an <a target="_blank" href="http://www.it-slav.net/blogs/2009/10/05/an-advanced-gpld-rule-engine-nodebrain/">earlier article</a> described the ruleset for this implementation but now I&nbsp;will show how the integration can be done.</p>
<p>&nbsp;</p>
<h2>Scenario</h2>
<p>The scenario is a webshop with:</p>
<ul>
<li>5 frontend webservers</li>
<li>2 application servers</li>
<li>3 databasservers</li>
</ul>
<p>Management want to monitor how the webshop is doing. They do not want to know if a redundant part is down instead management want to have the overview of the webshop status.<span id="more-1423"></span></p>
<p>A management consultant is hired and do an investigation and after a ridiculous amount of money the following rules are defined:</p>
<ul>
<li>Webserver rules
<ul>
<li>If 3 or more webserver works the webservice is OK</li>
<li>If 2 webservers works the webservice is WARNING</li>
<li>If 1 webserver or less is working the webservice is CRITICAL</li>
</ul>
</li>
<li>Applicationserver rules
<ul>
<li>If 1 or 2 application servers works the application layer is OK</li>
<li>If zero application servers works the application layer is CRITICAL</li>
</ul>
</li>
<li>Database server rules
<ul>
<li>If 2 or more database server works the database layer is OK</li>
<li>if 1 database server works the database layer is WARNING</li>
<li>If no database servers works the database layer is CRITICAL</li>
</ul>
</li>
<li>&nbsp;The webserver layer, application layer and database layer should be viewed seperatly</li>
<li>The total webshop status has the highest status value of webserver layer, application layer and database layer</li>
</ul>
<p>I use Nagvis to illustrate the releationship between the layers.</p>
<p>&nbsp;</p>
<h3>Case 1</h3>
<p>The picture shows when everything is fine:</p>
<p><img height="335" width="826" class="aligncenter size-full wp-image-1435" title="Screenshot3" alt="Screenshot3" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/10/Screenshot31.png" /></p>
<h3>Case 2</h3>
<p>The rules in place:</p>
<ul>
<li>2 webservers CRITICAL and the webserverlayer is OK</li>
<li>1 appserver CRITICAL and the application layer is OK</li>
<li>2 databases are down and the database layer is WARNING</li>
<li>The total webshop status is WARNING because it has the highest status of the different layers</li>
</ul>
<p><img height="308" width="771" class="aligncenter size-full wp-image-1436" title="Screenshot4" alt="Screenshot4" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/10/Screenshot4.png" /></p>
<p>&nbsp;</p>
<h3>Case 3</h3>
<p>Now it has been even worse:</p>
<ul>
<li>4 webservers CRITICAL and the webserverlayer is CRITICAL</li>
<li>1 appserver CRITICAL and the application layer is OK</li>
<li>2 databases are down and the database layer is WARNING</li>
<li>The total webshop status is CRITICAL because it has the highest status of the different layers</li>
</ul>
<p>&nbsp;<img height="308" width="816" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/10/Screenshot5.png" alt="Screenshot5" title="Screenshot5" class="aligncenter size-full wp-image-1438" /></p>
<p>&nbsp;</p>
<h2>Conclusions</h2>
<p>This article shows the power of Open Source and what is possible todo when integration different projects with each other. A solution like this with one of the Big Four (IBM, BMC, CA, HP)&nbsp;would have cost alot when it comes to license and highly specialised consultants had to be hirered.</p>
<h1>&nbsp;</h1>
<h2>Links</h2>
<ul>
<li><a href="http://www.op5.com">Op5</a> A company that package and support enterprise class systems- and networkmanagement products</li>
<li><a href="http://www.nodebrain.org">NodeBrain</a>, A powerful GPL&#8217;d rule engine</li>
<li><a href="http://www.nagios.org">Nagios</a>, An enterprise class Monitoring sofware</li>
<li><a href="http://www.nagvis.org/">Nagvis</a>, Nagios Visualization addon</li>
</ul>
<p>&nbsp;</p>
<h1>&nbsp;</h1>
<h1>Implementation</h1>
<h2>Hosts and services</h2>
<p>The hosts and services are created:</p>
<ul>
<li>Webserver layer: 5 hosts each with 1 service</li>
<li>Application layer: 2 hosts each with 1 service</li>
<li>Database layer: 3 hosts each with 1 service</li>
<li>Webshop layer: 1 host called webshopcontainer and 4 services: webserversstatus, appsserverstatus, dbserversstatus and webshop status. The services represent each layer in the model and webshop is the total status of the webshop.</li>
</ul>
<p>To make it easy to control the status of all these devices I will use passive checks. So if I want to change the status of a service I&nbsp;just use the GUI&nbsp;and send in a passive check result. In real life active checks would have been used to monitor the different services.</p>
<p>&nbsp;</p>
<p>The result showing <strong>Service Detail</strong> using op5 developed Nagios GUI&nbsp;<a target="_blank" href="http://www.op5.org/community/projects/ninja">Ninja</a>:</p>
<p><img height="467" width="1209" class="aligncenter size-full wp-image-1431" title="screenshoot2" alt="screenshoot2" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/10/screenshoot2.png" /></p>
<p>&nbsp;</p>
<p>The statechanges are sent to NodeBrain via an eventhandler that sends the NodeBrain commands via a namedpipe:</p>
<p><code>#!/bin/sh<br />
#<br />
# Event handler script for sending nagios data to nodebrain<br />
#<br />
# This script has these arguments $SERVICESTATEID$ $SERVICESTATETYPE$ $SERVICEATTEMPT$ $SERVICEDESC$ $HOSTNAME$<br />
NODEBRAINPIPE=/opt/plugins/custom/nodebrainpipe<br />
DATE=`date`<br />
echo &quot;$DATE SERVICESTATEID=$1 SERVICESTATETYPE=$2 SERVICEATTEMPT=$3 SERVICEDESC=$4 HOSTNAME=$5&quot; &gt;&gt; /tmp/eventhandler_out</p>
<p># What state is the service in?<br />
case &quot;$1&quot; in<br />
OK)<br />
&nbsp;&nbsp;&nbsp; # The service just came back up<br />
&nbsp;&nbsp;&nbsp; # Send ok to nodebrain<br />
&nbsp;&nbsp;&nbsp; echo &quot;assert $4=0;&quot; &gt; $NODEBRAINPIPE<br />
&nbsp;&nbsp;&nbsp; echo &quot;assert $4=0;&quot; &gt;&gt; /tmp/eventhandler_out<br />
&nbsp;&nbsp;&nbsp; ;;<br />
WARNING)<br />
&nbsp;&nbsp;&nbsp; # We don't really care about warning states, since the service is probably still running...<br />
&nbsp;&nbsp;&nbsp; ;;<br />
UNKNOWN)<br />
&nbsp;&nbsp;&nbsp; # We don't know what might be causing an unknown error, so don't do anything...<br />
&nbsp;&nbsp;&nbsp; ;;<br />
CRITICAL)<br />
&nbsp;&nbsp;&nbsp; # Is this a &quot;soft&quot; or a &quot;hard&quot; state?<br />
&nbsp;&nbsp;&nbsp; case &quot;$2&quot; in<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br />
&nbsp;&nbsp;&nbsp; SOFT)<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; # We're in a &quot;soft&quot; state, meaning that Nagios is in the middle of retrying the<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; # check before it turns into a &quot;hard&quot; state and contacts get notified...<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; # Don't do anything&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ;;<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br />
&nbsp;&nbsp;&nbsp; # The HTTP service somehow managed to turn into a hard error without getting fixed.<br />
&nbsp;&nbsp;&nbsp; # It should have been restarted by the code above, but for some reason it didn't.<br />
&nbsp;&nbsp;&nbsp; # Let's give it one last try, shall we?&nbsp; <br />
&nbsp;&nbsp;&nbsp; # Note: Contacts have already been notified of a problem with the service at this<br />
&nbsp;&nbsp;&nbsp; # point (unless you disabled notifications for this service)<br />
&nbsp;&nbsp;&nbsp; HARD)<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; # AHA! Hard state, send data to nodebrain<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; echo &quot;assert $4=2;&quot; &gt; $NODEBRAINPIPE<br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; echo &quot;assert $4=2;&quot; &gt;&gt;/tmp/eventhandler_out <br />
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ;;<br />
&nbsp;&nbsp;&nbsp; esac<br />
&nbsp;&nbsp;&nbsp; ;;<br />
esac</p>
<p>exit 0</code></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>The Nodebrainrules, that has all the logic and opens the namedpipe for commands:</p>
<p><code>#!/usr/local/bin/nb -d<br />
# <br />
-rm webshop.log<br />
set log=&quot;webshop.log&quot;,out=&quot;.&quot;;<br />
declare indata identity owner;<br />
define webshop node pipe.server(&quot;indata@nodebrainpipe&quot;);</p>
<p>#Start with webservers<br />
#Set OK<br />
assert weba=0;<br />
assert webb=0;<br />
assert webc=0;<br />
assert webd=0;<br />
assert webe=0;<br />
assert&nbsp; webserversstatus=0;</p>
<p>#define webserver rules<br />
#5 frontwebservers, if 3 or more ok status is ok<br />
#if 2 is ok, status warning<br />
#if 1 or 0 ok, status critical<br />
define webservers cell weba+webb+webc+webd+webe;</p>
<p>define webserversok on(webservers&lt;=4) webserversstatus=0;<br />
define webseroksend on(webserversstatus=0):-./send_to_monitor.sh webserversstatus 0 &quot;OK: Websservers are fine&quot;;</p>
<p>define webserverswarning on(webservers&gt;4 and webservers&lt;8) webserversstatus=1;<br />
define webserverswarningsend on(webserversstatus=1):-./send_to_monitor.sh webserversstatus 1 &quot;WARNING: Webservers have problems&quot;;</p>
<p>define webserverscritical on(webservers&gt;=8) webserversstatus=2;<br />
define webserverscriticalsend on(webserversstatus=2):-./send_to_monitor.sh webserversstatus 2 &quot;CRITICAL: Webservers have serious problems &quot;;</p>
<p>#appservers<br />
assert appa=0;<br />
assert appb=0;<br />
assert appserversstatus=0;<br />
#2 appservers, 1 down is ok, 2 down critical<br />
define appservers cell appa+appb;</p>
<p>define appserversok on(appservers&lt;=2) appserversstatus=0;<br />
define appserversoksend on(appserversstatus=0):-./send_to_monitor.sh appserversstatus 0 &quot;OK: Appservers are fine&quot;;</p>
<p>define appserverscritical on(appservers&gt;2) appserversstatus=2;<br />
define appserverscriticalsend on(appserversstatus=2):-./send_to_monitor.sh appserversstatus 2 &quot;CRITICAL: Appservers have serious problems&quot;;</p>
<p>#Databaseservers<br />
assert dba=0;<br />
assert dbb=0;<br />
assert dbc=0;<br />
assert dbserversstatus=0;<br />
#3 db servers<br />
#if 2 or more ok, status ok<br />
#if 1 ok, status warning<br />
define dbservers cell dba+dbb+dbc;</p>
<p>define dbserversok on(dbservers&lt;=2) dbserversstatus=0;<br />
define dbserversoksend on(dbserversstatus=0):-./send_to_monitor.sh dbserversstatus 0 &quot;OK: DataBaseservers are fine&quot;;</p>
<p>define dbserverswarning on(dbservers&gt;=4 and dbservers &lt;6)dbserversstatus=1;<br />
define dbserverswarningsend on(dbserversstatus=1):-./send_to_monitor.sh dbserversstatus 1 &quot;WARNING: DataBaseservers have problems&quot;;</p>
<p>define dbservercritical on(dbservers&gt;=6)dbserversstatus=2;<br />
define dbservercriticalsend on(dbserversstatus=2):-./send_to_monitor.sh dbserversstatus 2 &quot;CRITICAL: DataBaseservers have serious problems&quot;;</p>
<p>#Total rules<br />
assert webshopstatus=0;<br />
#If all serverstatus ok, the whole webshop is ok<br />
define webshopok on(webserversstatus=0 and appserversstatus=0 and dbserversstatus=0) webshopstatus=0;<br />
define webshopoksend on(webshopstatus=0):-./send_to_monitor.sh webshopstatus 0 &quot;OK: Webshop is fine&quot;;<br />
#If any serverstatus is critical the whole webshop is critical<br />
define webshopscritical on(webserversstatus=2 or appserversstatus=2 or dbserversstatus=2) webshopstatus=2;<br />
define webshopscriticalsend on(webshopstatus=2):-./send_to_monitor.sh webshopstatus 2 &quot;CRITICAL: Webshop has serious problems&quot;;<br />
#If not any serverstatuscritical and in warning, the whole shop is warning.<br />
define webshopwarning on((!webserversstatus=2 and !appserversstatus=2 and !dbserversstatus=2) and (webserversstatus=1 or dbserversstatus=1)) webshopstatus=1; <br />
define webshopwarningsend on(webshopstatus=1):-./send_to_monitor.sh webshopstatus 1 &quot;WARNING: Webshop has some problems&quot;;</code><br />
&nbsp;</p>
<p>&nbsp;</p>
<p>The NodeBrain rules runs this script when fired:</p>
<p><code>#!/bin/sh</p>
<p>HOSTNAME=webshopcontainer<br />
SERVICEDESC=$1<br />
STATUS=$2<br />
MESSAGE=$3<br />
</code></p>
<p><code>now=`date +%s`<br />
commandfile='/opt/monitor/var/rw/nagios.cmd'<br />
/usr/bin/printf &quot;[%lu] PROCESS_SERVICE_CHECK_RESULT;$HOSTNAME;$SERVICEDESC;$STATUS;$MESSAGE\n&quot; $now &gt; $commandfile</code></p>
<p>
&nbsp;</p>
<p>The Nagios or op5 Monitor hosts.cfg</p>
<p><code>###############################################################################<br />
#&nbsp; Generated by op5 Monitor webconfiguration exporter<br />
#<br />
#&nbsp; Exported 2009-10-22 19:33 by monitor<br />
#</p>
<p>
# host template 'Dummy-template'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; initial_state&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o<br />
&nbsp;&nbsp;&nbsp; hostgroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NodeBrainDemo<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check-host-alive<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5<br />
&nbsp;&nbsp;&nbsp; check_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5<br />
&nbsp;&nbsp;&nbsp; retry_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; obsess_over_host&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; check_freshness&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; active_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; passive_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; process_perf_data&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_status_information&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_nonstatus_information&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; notification_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; notification_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; notification_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d,u,r,f<br />
&nbsp;&nbsp;&nbsp; notifications_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; stalking_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; register&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host template 'default-host-template'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-host-template<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check-host-alive<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br />
&nbsp;&nbsp;&nbsp; check_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5<br />
&nbsp;&nbsp;&nbsp; retry_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; check_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; active_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; passive_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; process_perf_data&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_status_information&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_nonstatus_information&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; notification_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; notification_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; notification_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d,u,r,f,s<br />
&nbsp;&nbsp;&nbsp; notifications_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; register&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'app-host-a'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; app-host-a<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; App Host A<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; hostgroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NodeBrainDemo<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'app-host-b'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; app-host-b<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; App Host B<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'db-host-a'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-a<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DB Host A<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'db-host-b'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-b<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DB Host B<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'db-host-c'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-c<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DB Host C<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'web-host-a'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-a<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Web Host A<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'web-host-b'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-b<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Web Host B<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'web-host-c'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-c<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Web Host C<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'web-host-d'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-d<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Web Host D<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'web-host-e'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-e<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Web Host E<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># host 'webshopcontainer'<br />
define host{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 127.0.0.1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; }</code><br />
&nbsp;</p>
<p>&nbsp;</p>
<p>The Nagios or op5 Monitor services.cfg</p>
<p><code>###############################################################################<br />
#&nbsp; Generated by op5 Monitor webconfiguration exporter<br />
#<br />
#&nbsp; Exported 2009-10-22 19:33 by monitor<br />
#</p>
<p># service template 'Dummy-service-template'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; display_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; is_volatile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; initial_state&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; check_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retry_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; active_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; passive_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; check_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; parallelize_check&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; obsess_over_service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; check_freshness&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; event_handler_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; process_perf_data&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_status_information&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_nonstatus_information&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; notification_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; notification_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; notification_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c,w,u,r,f<br />
&nbsp;&nbsp;&nbsp; notifications_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; stalking_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; register&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># service template 'default-service'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; is_volatile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br />
&nbsp;&nbsp;&nbsp; check_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5<br />
&nbsp;&nbsp;&nbsp; retry_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; active_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; passive_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; check_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; event_handler_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; process_perf_data&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_status_information&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; retain_nonstatus_information&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; notification_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; notification_period&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24x7<br />
&nbsp;&nbsp;&nbsp; notification_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c,w,u,r,f,s<br />
&nbsp;&nbsp;&nbsp; notifications_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; register&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>
####################################################<br />
#<br />
# Services for host app-host-a<br />
#</p>
<p># service 'appa'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; app-host-a<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appa<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; parallelize_check&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; obsess_over_service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; check_freshness&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; flap_detection_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; support-group<br />
&nbsp;&nbsp;&nbsp; stalking_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host app-host-b<br />
#</p>
<p># service 'appb'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; app-host-b<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appb<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host db-host-a<br />
#</p>
<p># service 'dba'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-a<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dba<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host db-host-b<br />
#</p>
<p># service 'dbb'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-b<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dbb<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host db-host-c<br />
#</p>
<p># service 'dbc'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; db-host-c<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dbc<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host web-host-a<br />
#</p>
<p># service 'weba'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-a<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; weba<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host web-host-b<br />
#</p>
<p># service 'webb'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-b<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webb<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host web-host-c<br />
#</p>
<p># service 'webc'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-c<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webc<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host web-host-d<br />
#</p>
<p># service 'webd'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-d<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webd<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host web-host-e<br />
#</p>
<p># service 'webe'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web-host-e<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webe<br />
&nbsp;&nbsp;&nbsp; check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br />
&nbsp;&nbsp;&nbsp; event_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eventhandler_send_to_nodebrain<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p>####################################################<br />
#<br />
# Services for host webshopcontainer<br />
#</p>
<p># service 'appserversstatus'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appserversstatus<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># service 'dbserversstatus'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dbserversstatus<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># service 'webserversstatus'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webserversstatus<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</p>
<p># service 'webshopstatus'<br />
define service{<br />
&nbsp;&nbsp;&nbsp; use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dummy-service-template<br />
&nbsp;&nbsp;&nbsp; host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopcontainer<br />
&nbsp;&nbsp;&nbsp; service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshopstatus<br />
&nbsp;&nbsp;&nbsp; servicegroups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; webshop<br />
&nbsp;&nbsp;&nbsp; flap_detection_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<br />
&nbsp;&nbsp;&nbsp; }</code></p>
<p>
&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/10/22/rule-engine-integration-with-nagios-using-nodebrain/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>op5 bugtracker online and open for registration</title>
		<link>http://www.it-slav.net/blogs/2009/10/02/op5-bugtracker-online-and-open-for-registration/</link>
		<comments>http://www.it-slav.net/blogs/2009/10/02/op5-bugtracker-online-and-open-for-registration/#comments</comments>
		<pubDate>Fri, 02 Oct 2009 11:38:24 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Logserver]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[op5 Statistics]]></category>
		<category><![CDATA[merlin]]></category>
		<category><![CDATA[ninja]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1385</guid>
		<description><![CDATA[https://bugs.op5.com/ is now also open for external users to sign up. By signing up you can post bug and feature requests, post bug-notes etc.

Before doing so, please check out the &#34;How to Submit Bug/Feature&#34; documentation available from within the bug tracker.

Note: op5 opensource projects Merlin, Ninja and Nacoma are for now available as categories on [...]]]></description>
			<content:encoded><![CDATA[<pre wrap=""><a href="https://bugs.op5.com/" class="moz-txt-link-freetext">https://bugs.op5.com/</a> is now also open for external users to sign up. By signing up you can post bug and feature requests, post bug-notes etc.

Before doing so, please check out the &quot;How to Submit Bug/Feature&quot; documentation available from within the bug tracker.

Note: op5 opensource projects Merlin, Ninja and Nacoma are for now available as categories on Project: op5 Monitor, it's simply to make it easy for us to show a product roadmap/changelog although it might be a bit &quot;unlogical&quot; for people using only Merlin.</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/10/02/op5-bugtracker-online-and-open-for-registration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>op5 announces the release of op5 Monitor 4.2</title>
		<link>http://www.it-slav.net/blogs/2009/09/15/op5-announces-the-release-of-op5-monitor-4-2/</link>
		<comments>http://www.it-slav.net/blogs/2009/09/15/op5-announces-the-release-of-op5-monitor-4-2/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 09:00:10 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[ninja]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1346</guid>
		<description><![CDATA[op5 AB is a world leading OSM &#8211; Open Source Management &#8211; company that delivers software based on open source for control of IT systems and networks. The award winning op5 Monitor is now released with important enhancements that will enable customers and other vendors to further improve usability and integration for optimized IT monitoring. [...]]]></description>
			<content:encoded><![CDATA[<p><em>op5 AB is a world leading OSM &#8211; Open Source Management &#8211; company that delivers software based on open source for control of IT systems and networks. The award winning op5 Monitor is now released with important enhancements that will enable customers and other vendors to further improve usability and integration for optimized IT monitoring. </em></p>
<p>&nbsp;</p>
<p>op5 Monitor is based on Nagios*, the industry standard for enterprise-class IT infrastructure monitoring. Until now, op5 Monitor has had to rely on the basics of standard Nagios Graphical User Interface (GUI) for presentation and overall user experience. With the release of op5 Monitor 4.2 we include a fully functional preview of a brand new GUI, now based on the Ninja Open Source project. The new GUI is based on a modern PHP architecture and is now shipped for real operation testing.<span id="more-1346"></span></p>
<p>&nbsp;</p>
<p>Usability, flexibility and visualization probably stands for more then 80% of overall customer value. Our solutions for full control of our customers IT systems hold a huge amount of both historical data and instant events. Making this information accessible and easy to understand for as many as possible is the single most effective value for our customers. And who is better to give us important feedback on GUI related features and functions then our customers? This is why we now choose to include an early version for test, evaluation and feedback purposes, all to secure the best for the coming official release of Monitor 5.0 later this year, says Jan Josephson, CEO op5 AB.</p>
<p>&nbsp;</p>
<p>The new GUI with its flexible interface based on the PHP framework makes it much easier to provide customizations for customers specific needs. With the introduction of widget and support session based authentication it is now possible to fully personalize views and settings. The widget technology further provides a future standard way for two way synchronization and presentation of customer unique data and the presentation of it.</p>
<p>&nbsp;</p>
<p>The ability to search, sort and filter vast data volumes has been greatly improved with pagination for views of hosts and services and the possibility to sort by column. The new improved search feature includes auto suggestion and let you search on hosts, services host groups and service groups. <br />
These changes greatly improves the possibilities to answer to customer needs and to develop customized features that has not been possible until now due to the restrictions from the old GUI.<br />
A new module for network visualization (the NagVis project) has been included in op5 Monitor 4.2. You can now visualize your infrastructure using three different map types;</p>
<ul>
<li>Auto map, a auto drawn topology map using parent / child relationships.</li>
<li>Static Map makes it possible to put any object (host, service, host group or service group) on an image of choice.</li>
<li>Geo map, uses Google maps API, drawing a map by using addresses or gps coordinates on your monitored objects. Object and status information as well as links can be included in the map. The maps can be visualized as widgets on the tactical overview or be used on big monitors in operation centers.</li>
<li>Largest OSS-project in Network Monitoring, Nagios.</li>
</ul>
<p>&nbsp;</p>
<p>About op5 AB op5 AB is a world leading OSM &#8211; Open Source Management &#8211; company that delivers software based on open source for control of IT systems and networks. Its main products are op5 Monitor, op5 Statistics and op5 LogServer. The products are based on open source code that op5 further develops, packages, and sells as complete products and systems with services and support. p5 has a large selection of primarily European clients from different market segments for example AGA Linde Gas, The Swedish Customs Service (Tullverket) and other parastatals, several county councils, municipalities and municipal companies. op5 was founded in 2003. The company is based in Sweden with offices in Stockholm and Gothenburg.</p>
<p>&nbsp;</p>
<p><a href="http://www.op5.com/">www.op5.com</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/09/15/op5-announces-the-release-of-op5-monitor-4-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ninja, the new Nagios GUI, preview</title>
		<link>http://www.it-slav.net/blogs/2009/09/12/ninja-the-new-nagios-gui-preview/</link>
		<comments>http://www.it-slav.net/blogs/2009/09/12/ninja-the-new-nagios-gui-preview/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 13:27:33 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[geomap]]></category>
		<category><![CDATA[google maps]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[Nagios gui]]></category>
		<category><![CDATA[ninja]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1314</guid>
		<description><![CDATA[&#160;
Next week, op5 will release the new Nagios GUI called Ninja. The license is GPL and several people has reported the GUI work perfectly well on vanilla Nagios. Ninja uses a database backend. Merlin, another op5 developed software feeds the Nagios information into the database.
Links:

op5 -OpenSource based management software company
Ninja- Nagios Is Now Just Awesome
Merlin [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p>Next week, op5 will release the new Nagios GUI called Ninja. The license is GPL and several people has reported the GUI work perfectly well on vanilla Nagios. Ninja uses a database backend. Merlin, another op5 developed software feeds the Nagios information into the database.</p>
<p>Links:</p>
<ul>
<li><a href="http://www.op5.com">op5</a> -OpenSource based management software company</li>
<li><a href="http://www.op5.org/community/projects/ninja">Ninja</a>- Nagios Is Now Just Awesome</li>
<li><a href="http://www.op5.org/op5media/op5.org/merlin/merlin_100x100.png">Merlin</a> &#8211; Module for Effortless Redundancy and Loadbalancing In Nagios</li>
<li><a href="https://beta.op5.com/ninja">Try</a> &#8211; Ninja GUI</li>
</ul>
<p>Some screenshoots below:</p>
<p>&nbsp;</p>
<p>&nbsp;Geomap, based on google maps</p>
<p><img height="448" width="943" class="aligncenter size-full wp-image-1325" title="geomap" alt="geomap based in googlemaps" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/geomap3.png" /></p>
<p>&nbsp;<span id="more-1314"></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Tactical overview, with widgets that could be dragged and dropped<img class="aligncenter size-full wp-image-1328" title="tacticaloverview" alt="tacticaloverview" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/tacticaloverview.png" style="width: 951px; height: 442px;" /></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Host details</p>
<p><img class="aligncenter size-full wp-image-1331" title="hostdetails" alt="hostdetails" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/hostdetails.png" style="width: 956px; height: 441px;" /></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Nagvis integration</p>
<p><img height="663" width="878" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/nagvis-demo.png" alt="nagvis-demo" title="nagvis-demo" class="aligncenter size-full wp-image-1333" /></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/09/12/ninja-the-new-nagios-gui-preview/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Speedup wordpress blogs</title>
		<link>http://www.it-slav.net/blogs/2009/09/05/speedup-wordpress-blogs/</link>
		<comments>http://www.it-slav.net/blogs/2009/09/05/speedup-wordpress-blogs/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 07:13:34 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[tune]]></category>
		<category><![CDATA[webinject]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1283</guid>
		<description><![CDATA[I noticed that my blog become slower and slower by using op5 Monitor and webinject, see previous article. From installation 2.5 seconds to over 7.5 seconds to run my testcases. The most annoying was that the it was a very linear increase see graphs below. My first try was to tune MySQL
By installing wp-cache the [...]]]></description>
			<content:encoded><![CDATA[<p>I noticed that my blog become slower and slower by using <a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a> and <a target="_blank" href="http://www.webinject.org/">webinject</a>, see<a target="_blank" href="http://www.it-slav.net/blogs/2009/03/16/wordpress-monitoring-with-nagios-or-op5-monitor-using-webinject/"> previous article</a>. From installation 2.5 seconds to over 7.5 seconds to run my testcases. The most annoying was that the it was a very linear increase see graphs below. My first try was to <a target="_blank" href="http://www.it-slav.net/blogs/2009/03/03/mysql-tuning/">tune</a> MySQL</p>
<p>By installing <a target="_blank" href="http://mnm.uib.es/gallir/wp-cache-2/">wp-cache </a>the testcase went down to 0.4 seconds.</p>
<p>&nbsp;</p>
<p>&nbsp;The drawback is that my counter widget is getting updated every hour instead of every reload of the webpage.</p>
<p>&nbsp;</p>
<p>Take a peak at some nice graphs showing that I&nbsp;stopped the increasing loading time and got a speedup from 7.5 seconds to 0.4 seconds:</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><img height="221" width="581" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/24-hours.png" alt="24-hours" title="24-hours" class="aligncenter size-full wp-image-1284" /></p>
<p><span id="more-1283"></span></p>
<p>&nbsp;</p>
<p><img height="207" width="581" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/one-week.png" alt="one-week" title="one-week" class="aligncenter size-full wp-image-1285" /></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><img height="207" width="581" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/09/onemonth.png" alt="onemonth" title="onemonth" class="aligncenter size-full wp-image-1286" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/09/05/speedup-wordpress-blogs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Monitoring VMware ESX 3.x, ESXi, vSphere 4 and vCenter Server with Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/09/03/monitoring-vmware-esx-3-x-esxi-vsphere-4-and-vcenter-server-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/09/03/monitoring-vmware-esx-3-x-esxi-vsphere-4-and-vcenter-server-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 18:08:58 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[esx3.x]]></category>
		<category><![CDATA[esxi]]></category>
		<category><![CDATA[vCenter]]></category>
		<category><![CDATA[VmWare]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1279</guid>
		<description><![CDATA[Op5 has written an excellent article howto monitor Esx3.x, ESXi, vSphere 4 and vCenter Server with op5 Monitor. This article is op5 Monitor centric but op5 Monitor is based on Nagios so this article can be used to implement Nagios vmware monitoring.
The plugin used to gather the information is GPLd and developed by op5.
Links

The article [...]]]></description>
			<content:encoded><![CDATA[<p>Op5 has written an <a target="_blank" href="http://www.op5.com/support/documentation/how-to/400-monitoring-vmware-esx-3x-esxi-vsphere-4-and-vcenter-server">excellent article</a> howto monitor Esx3.x, ESXi, vSphere 4 and vCenter Server with <a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a>. This article is op5 Monitor centric but op5 Monitor is based on <a target="_blank" href="http://www.nagios.org">Nagios</a> so this article can be used to implement Nagios vmware monitoring.</p>
<p>The <a target="_blank" href="http://git.op5.org/git/?p=nagios/op5plugins.git;a=blob_plain;f=check_esx3.pl;hb=HEAD">plugin</a> used to gather the information is GPLd and developed by op5.</p>
<h3>Links</h3>
<ul>
<li>The <a target="_blank" href="http://www.op5.com/support/documentation/how-to/400-monitoring-vmware-esx-3x-esxi-vsphere-4-and-vcenter-server">article </a>describing howto monitor vmware.</li>
<li><a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a> &#8211; Enterprise class supported monitoring solution based on Nagios.</li>
<li><a href="http://www.nagios.org">Nagios</a> &#8211; OpenSource Enterprise class monitoring solution.</li>
<li>Check_esx <a target="_blank" href="http://git.op5.org/git/?p=nagios/op5plugins.git;a=blob_plain;f=check_esx3.pl;hb=HEAD">plugin</a> created by op5</li>
<li><a target="_blank" href="http://www.op5.com">op5</a> &#8211; The company behind he plugin.</li>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/09/03/monitoring-vmware-esx-3-x-esxi-vsphere-4-and-vcenter-server-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Skype for SMS notification for Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/06/26/using-skype-for-sms-notification-for-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/06/26/using-skype-for-sms-notification-for-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Fri, 26 Jun 2009 09:54:34 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[nagios notification]]></category>
		<category><![CDATA[skype]]></category>
		<category><![CDATA[skype nagios]]></category>
		<category><![CDATA[skype notification]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1158</guid>
		<description><![CDATA[An interesting article describing howto use Skype to send SMS notification for Nagios or op5 Monitor can be find here:
http://wiki.nagios.org/index.php/SkypeSmsNotification
My recommendation is to use an GSM modem to send SMS, because if the network is down no SMS can be sent with this solution and SMS is normally used as an alternative alarm route.
Another aspect [...]]]></description>
			<content:encoded><![CDATA[<p>An interesting article describing howto use Skype to send SMS notification for Nagios or op5 Monitor can be find here:</p>
<p><a target="_blank" href="http://wiki.nagios.org/index.php/SkypeSmsNotification">http://wiki.nagios.org/index.php/SkypeSmsNotification</a></p>
<p>My recommendation is to use an GSM modem to send SMS, because if the network is down no SMS can be sent with this solution and SMS is normally used as an alternative alarm route.</p>
<p>Another aspect is that Skype is using propertiary protocols and that should be avoided.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/06/26/using-skype-for-sms-notification-for-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Nagios or op5 Monitor eventhandler to start a service that has stopped</title>
		<link>http://www.it-slav.net/blogs/2009/06/15/using-nagios-or-op5-monitor-eventhandler-to-start-a-service-that-has-stopped/</link>
		<comments>http://www.it-slav.net/blogs/2009/06/15/using-nagios-or-op5-monitor-eventhandler-to-start-a-service-that-has-stopped/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 19:03:01 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[MythTV]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1138</guid>
		<description><![CDATA[Background
I use MythTV quite frequently and noticed that it is instable when using sasc-ng as a decoder to decrypt encrypted DVB-T channels. So approximatly every third day the MythTVbackend server stops and need to be started again. I have wriiten an earlier article about howto monitor MythTV with Nagios or op5 Monitor so I get [...]]]></description>
			<content:encoded><![CDATA[<h2>Background</h2>
<p>I use MythTV quite frequently and noticed that it is instable when using <a target="_blank" href="https://opensvn.csie.org/traccgi/sascng/">sasc-ng</a> as a decoder to decrypt encrypted DVB-T channels. So approximatly every third day the MythTVbackend server stops and need to be started again. I have wriiten an <a target="_blank" href="http://www.it-slav.net/blogs/?p=651">earlier article</a> about howto monitor MythTV with Nagios or op5 Monitor so I get noticed that it has stopped. But I need to manually start it again. This article describe howto make Nagios or op5 Monitor to start a stopped MythTVbackend. It can be used for starting almost any service.</p>
<p>I have used the examples provided by Ethan at <a target="_blank" href="http://support.nagios.com/knowledge-base/official-documentation">Nagios official documentation</a> describing <a target="_blank" href="http://nagios.sourceforge.net/docs/3_0/eventhandlers.html">eventhandlers</a>.</p>
<p>Normally it is not recommended to let a tool like Nagios or op5 Monitor start a service that has stopped, because it is probably a reason why the service has stopped and the correct procedure is to fix the root cause of the problem, not the symptom.</p>
<p>The MythTV backend runs on one machine called lala (after a character in Teletubbies) which is not the same as the Nagios or op5 Monitor server. I use nrpe to run the start script i.e.</p>
<pre>
 /etc/init.d/mythtv-backend start
</pre>
<p>There is several options here but I already setup the nrpe agent and it is simple to make Nagios or op5 Monitor to use nrpe to run a script.<span id="more-1138"></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h2>Implementation</h2>
<p>I used the script I found at Nagios documentation about <a target="_blank" href="http://nagios.sourceforge.net/docs/3_0/eventhandlers.html">eventhandlers</a> as a base and modiied it slightly.</p>
<p>&nbsp;</p>
<h3>At my op5 Monitor machine</h3>
<pre>
/opt/plugins/custom/restart-mythtv-lala.sh
</pre>
<pre>
#!/bin/sh
#
# Event handler script for restarting the mythTVbackend server on lala
#
# Note: This script will only restart the mythtvbackend if the service is
#       retried 2 times (in a &quot;soft&quot; state) or if the service somehow
#       manages to fall into a &quot;hard&quot; error state.
#

# What state is the mythbackend service in?
case &quot;$1&quot; in
OK)
	# The service just came back up, so don't do anything...
	;;
WARNING)
	# We don't really care about warning states, since the service is probably still running...
	;;
UNKNOWN)
	# We don't know what might be causing an unknown error, so don't do anything...
	;;
CRITICAL)
	# Aha!  The HTTP service appears to have a problem - perhaps we should restart the server...

	# Is this a &quot;soft&quot; or a &quot;hard&quot; state?
	case &quot;$2&quot; in

	# We're in a &quot;soft&quot; state, meaning that Nagios is in the middle of retrying the
	# check before it turns into a &quot;hard&quot; state and contacts get notified...
	SOFT)

		# What check attempt are we on?  We don't want to restart the web server on the first
		# check, because it may just be a fluke!
		case &quot;$3&quot; in

		# Wait until the check has been tried 3 times before restarting the web server.
		# If the check fails on the 4th time (after we restart the web server), the state
		# type will turn to &quot;hard&quot; and contacts will be notified of the problem.
		# Hopefully this will restart the web server successfully, so the 4th check will
		# result in a &quot;soft&quot; recovery.  If that happens no one gets notified because we
		# fixed the problem!
		2)
			echo &quot;`date` Restarting mythtv service (2rd soft critical state)...&quot; &gt;&gt; /tmp/mythtvstart
			# Call the init script to restart the mythbackend server
			#/etc/rc.d/init.d/httpd restart
			#date &gt;&gt; /tmp/mythtvstart
			/opt/plugins/check_nrpe -H lala -c start_mythtvbackend
			;;
			esac
		;;

	# The mythtvbackend service somehow managed to turn into a hard error without getting fixed.
	# It should have been restarted by the code above, but for some reason it didn't.
	# Let's give it one last try, shall we?
	# Note: Contacts have already been notified of a problem with the service at this
	# point (unless you disabled notifications for this service)
	HARD)
		echo &quot;`date` Restarting mythtv service (hard state)...&quot; &gt;&gt; /tmp/mythtvstart
		# Call the init script to restart the HTTPD server
		#/etc/rc.d/init.d/httpd restart
		#date &gt;&gt; /tmp/mythtvstart
		/opt/plugins/check_nrpe -H lala -c start_mythtvbackend
		;;
	esac
	;;
esac
exit 0
</pre>
<p>&nbsp;</p>
<p>&nbsp;</p>
<pre>
/opt/monitor/misccomands.cfg</pre>
<pre>
# command 'restart-mythtv-lala'
define command{
    command_name                   restart-mythtv-lala
    command_line                   /opt/plugins/custom/start-mythtv-lala.sh $SERVICESTATE$ $SERVICESTATETYPE$ $SERVICEATTEMPT$
    }
</pre>
<p>&nbsp;</p>
<pre>
/opt/monitor/etc/services.cfg

# service 'Mythbackend'
define service{
    use                            default-service
    host_name                      lala
    service_description            Mythbackend
    check_command                  check_tcp!6543
    servicegroups                  MythTV,it-slav
    event_handler                  restart-mythtv-lala!$SERVICESTATE$ $SERVICESTATETYPE$ $SERVICEATTEMPT$
    contact_groups                 it-slav_sms,it-slav_jabber,it_slav_mail
    }
</pre>
<h3>At my mythbackend machine lala</h3>
<pre>
/etc/nrpe.d/mycommands.cfg
command[start_mythtvbackend]=/usr/bin/sudo /etc/init.d/mythtv-backend start

/etc/sudoers
nobody ALL= (root) NOPASSWD:/etc/init.d/mythtv-backend start
</pre>
<address>Notice that my nrpe agent run as user nobody</address>
<address>&nbsp;</address>
<address>&nbsp;</address>
<address>&nbsp;</address>
<address>&nbsp;</address>
<h2>Test</h2>
<p>I stopped the mythtvbackend by running:</p>
<pre>
peter@lala:/etc/nrpe.d$ date
Mon Jun 15 20:40:55 CEST 2009
peter@lala:/etc/nrpe.d$ sudo /etc/init.d/mythtv-backend stop
 * Stopping MythTV server: mythbackend
</pre>
<p>And run</p>
<pre>
[root@op5 ~]# tail -f /tmp/mythtvstart
Mon Jun 15 20:47:09 CEST 2009 Restarting mythtv service (2rd soft critical state)...
</pre>
<p>YES it works!</p>
<p>&nbsp;</p>
<h2>Links:</h2>
<ul>
<li><a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a> a Nagios based supported enterprise Monitoring software.</li>
<li><a target="_blank" href="http://www.mythtv.org">MythTV</a> a free OpenSource Digital Video Recorder</li>
<li><a href="http://www.nagios.org">Nagios</a> Open Source Monitoring</li>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/06/15/using-nagios-or-op5-monitor-eventhandler-to-start-a-service-that-has-stopped/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Free Nagios plugins from op5</title>
		<link>http://www.it-slav.net/blogs/2009/06/09/free-nagios-plugins-from-op5/</link>
		<comments>http://www.it-slav.net/blogs/2009/06/09/free-nagios-plugins-from-op5/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 07:17:10 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Hints]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1134</guid>
		<description><![CDATA[op5 develops plugins for op5 Monitor, based on Nagios. As a courtesy to the community the plugins developed are free and can be downloaded from:
http://www.op5.org/community/projects/op5-plugins
The plugins is also located in a Git repository and can be checked out from:
http://git.op5.org/git/
]]></description>
			<content:encoded><![CDATA[<p>op5 develops plugins for op5 Monitor, based on Nagios. As a courtesy to the community the plugins developed are free and can be downloaded from:</p>
<p><a href="http://www.op5.org/community/projects/op5-plugins" target="_blank">http://www.op5.org/community/projects/op5-plugins</a></p>
<p>The plugins is also located in a Git repository and can be checked out from:</p>
<p><a href="http://git.op5.org/git/" target="_blank">http://git.op5.org/git/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/06/09/free-nagios-plugins-from-op5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Merlin &#8211; Module for Endless Redundancy and Loadbalancing In Nagios</title>
		<link>http://www.it-slav.net/blogs/2009/05/15/merlin-module-for-endless-redundancy-and-loadbalancing-in-nagios/</link>
		<comments>http://www.it-slav.net/blogs/2009/05/15/merlin-module-for-endless-redundancy-and-loadbalancing-in-nagios/#comments</comments>
		<pubDate>Fri, 15 May 2009 14:10:54 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1090</guid>
		<description><![CDATA[The Merlin project was initially started to create an easy way to set up distributed Nagios installations allowing Nagios processes to exchange information directly as an alternative to the standard nagios way using NSCA. When starting the Ninja project we realised that we could continue the work on Merlin and adopt the project to function [...]]]></description>
			<content:encoded><![CDATA[<p>The Merlin project was initially started to create an easy way to set up distributed Nagios installations allowing Nagios processes to exchange information directly as an alternative to the <a href="http://nagios.sourceforge.net/docs/3_0/distributed.html">standard nagios way</a> using NSCA. When starting the <a href="http://www.op5.org/community/projects/ninja">Ninja</a> project we realised that we could continue the work on Merlin and adopt the project to function as backend for Ninja by adding support for storing the status information in a database, fault tolearance and some other cool things. This means that Merlin now are responsible for providing status data, acting as a backend, for the Ninja GUI.</p>
<p>Read more at <a href="http://www.op5.org/community/projects/merlin" target="_blank">http://www.op5.org/community/projects/merlin</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/05/15/merlin-module-for-endless-redundancy-and-loadbalancing-in-nagios/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>op5 Monitor tutorial part 2</title>
		<link>http://www.it-slav.net/blogs/2009/04/30/op5-monitor-tutorial-part-2/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/30/op5-monitor-tutorial-part-2/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 07:29:10 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Nagios]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=997</guid>
		<description><![CDATA[Demo of how the Nagios based network monitoring tool op5 Monitor works and how easy it is to use.  This part contains demo of the reports module and how to make SLA reports. 

 


]]></description>
			<content:encoded><![CDATA[<p><span class="description">Demo of how the Nagios based network monitoring tool <a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor</a> works and how easy it is to use.  This part contains demo of the reports module and how to make SLA reports. </span></p>
<p><span class="description"><br />
 </span></p>
<p>
<object width="425" height="344" data="http://www.youtube.com/v/lFj8u8WUmc8&amp;hl=sv&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/lFj8u8WUmc8&amp;hl=sv&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/30/op5-monitor-tutorial-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Monitor an IPsec VPN tunnel on OpenBSD with Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/04/27/monitor-an-ipsec-vpn-tunnel-on-openbsd-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/27/monitor-an-ipsec-vpn-tunnel-on-openbsd-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Mon, 27 Apr 2009 06:48:31 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[OpenBSD]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[ipsec]]></category>
		<category><![CDATA[vpn]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=1006</guid>
		<description><![CDATA[Background
This article describes how to monitor an IPSEC tunnel running on OpenBSD. I could not find any plugin already done so I created my own.
The pre req. for this article are:

A working Nagios or op5 Monitor setup
A IPsec VPN tunnel running on OpenBSD
A working NRPE agent at the OpenBSD box


&#160;
Theory
The way of getting the status [...]]]></description>
			<content:encoded><![CDATA[<h2>Background</h2>
<p>This article describes how to monitor an IPSEC tunnel running on OpenBSD. I could not find any plugin already done so I created my own.</p>
<p>The pre req. for this article are:</p>
<ul>
<li>A working <a href="http://www.nagios.org" target="_blank">Nagios</a> or <a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor</a> setup</li>
<li>A <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec&amp;apropos=0&amp;sektion=0&amp;manpath=OpenBSD+Current&amp;arch=i386&amp;format=html" target="_blank">IPsec VPN tunnel</a> running on <a href="http://www.openbsd.org" target="_blank">OpenBSD</a></li>
<li>A working NRPE agent at the OpenBSD box</li>
</ul>
<p><span id="more-1006"></span></p>
<p>&nbsp;</p>
<h2>Theory</h2>
<p>The way of getting the status of IPsec on OpenBSD is buy running:</p>
<pre>
ipsecctl -s s</pre>
<pre>
esp tunnel from x.x.x.x to y.y.y.y spi 0xe58a63d3 auth hmac-md5 enc 3des-cbc \
       authkey 0xabcdfghijklmnopqrstuvxyz \
       enckey 0xabcdfghijklmnopqrstuvxyz
esp tunnel from y.y.y.y to x.x.x.x spi 0x555f1f13 auth hmac-md5 enc 3des-cbc \
      authkey 0xabcdfghijklmnopqrstuvxyz \
      &nbsp;enckey 0xabcdfghijklmnopqrstuvxyz</pre>
<p>This shows that the IPsec tunnel between x.x.x.x and y.y.y.y is up.</p>
<p><em>Depending of the OpenBSD version the output will be different.</em></p>
<p>&nbsp;</p>
<p><em><br />
</em></p>
<h2>Plugin</h2>
<p>I put the plugin in /opt/plugins/custom at my OpenBSD box.</p>
<pre>
#!/bin/sh
#
# Copyright (C) 2009 Peter Andersson, peter@it-slav.net
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
#
# Very simple plugin that checks if a ipsec vpn is up between to ip-adresses
# Tested on OpenBSD 4.0
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see .
#
# Example use of this script:
# ./check_ipsecctl 10.1.1.1 10.2.1.1 &quot;VPN HQ&quot;
# OK: VPN HQ is up
#
# ./check_ipsecctl 10.1.1.1 10.2.1.1 &quot;VPN HQ&quot;
# CRITICAL: VPN HQ is down (No IP-SEC VPN from 10.1.1.1 to 10.2.1.1  No IP-SEC VPN from 10.2.1.1 to 10.1.1.1)
#
#
IPSECCTL=&quot;/sbin/ipsecctl -s sa&quot;
STATUS=0

LINE1=`$IPSECCTL | grep &quot;from $1 to $2&quot; `
if [ $? -eq 1 ]; then
        STATUS=2;
        OUTPUT1=&quot;No IP-SEC VPN from $1 to $2 &quot;
fi

LINE2=`$IPSECCTL | grep &quot;from $2 to $1&quot; `
if [ $? -eq 1 ]; then
        STATUS=2;
        OUTPUT2=&quot;No IP-SEC VPN from $2 to $1&quot;
fi

if [ $STATUS -eq 0 ]; then
        echo &quot;OK: $3 is up&quot;
        exit $STATUS
else
        echo &quot;CRITICAL: $3 is down ($OUTPUT1 $OUTPUT2)&quot;
        exit $STATUS
fi
</pre>
<h2>Nrpe config</h2>
<p>Nagios run check_ipsecctl via NRPE, it mus run as a privileged user and I use sudo, in /etc/nrpe.cfg</p>
<pre>
command[vpn_johan]=sudo /opt/plugins/custom/check_ipsecctl x.x.x.x y.y.y.y &quot;VPN Johan&quot;
</pre>
<p>x.x.x.x and y.y.y.y are the IP-addresses where the VPN tunnel terminates</p>
<p>&nbsp;</p>
<h2>Sudo</h2>
<p>Use sudoedit /etc/sudoers to modify the sudo config file:</p>
<p>nagios&nbsp; ALL=(root) NOPASSWD: /opt/plugins/custom/check_ipsecctl</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h2>Nagios or op5 Monitor configuration</h2>
<p>The VPN connection can be treated as a service running on the OpenBSD box, but in my opinion, the VPN&nbsp; should be treated as a host using the plugin above to check that the host is alive, and the hosts at the other end of the VPN connection should have the&nbsp; VPN tunnel as parent. The advantage is that if the VPN tunnel is down the hosts and services behind it is unreachable, which is the correct behavior.</p>
<p>&nbsp;</p>
<p>hosts.cfg</p>
<pre>
# host template 'default-hosttemplate-nrpe'
define host{
    name                           default-hosttemplate-nrpe
    check_command                  check_nrpe
    max_check_attempts             5
    obsess_over_host               0
    check_freshness                0
    active_checks_enabled          1
    passive_checks_enabled         1
    event_handler_enabled          1
    flap_detection_enabled         1
    flap_detection_options         n
    process_perf_data              1
    retain_status_information      1
    retain_nonstatus_information   1
    notification_interval          0
    notification_period            24x7
    notification_options           d,u,r,f
    notifications_enabled          1
    stalking_options               n
    register                       0
    }
# host 'vpn-johan'
define host{
    use                            default-hosttemplate-nrpe
    host_name                      vpn-johan
    alias                          vpn johan
    address                        10.1.1.1
    parents                        internet
    check_command                  check_nrpe!vpn_johan
    contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
    }
</pre>
<p>10.1.1.1 is the IP-adress to my OpenBSD box. The reason for using a template is that I&#8217;m using the webbased config tool that comes with op5 Monitor.</p>
<h2>The result</h2>
<p><img height="293" width="264" class="aligncenter size-full wp-image-1020" title="vpn-op5monitor" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/04/vpn-op5monitor.png" alt="vpn-op5monitor" /></p>
<h2>Links</h2>
<ul>
<li><a href="http://www.nagios.org" target="_blank">Nagios</a></li>
<li><a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor</a> a Nagios based full supported monitor solution</li>
<li><a href="http://www.openbsd.org" target="_blank">OpenBSD</a>, a FREE, multi-platform 4.4BSD-based UNIX-like operating system.</li>
<li><a href="http://www.ietf.org/proceedings/37/charters/ipsec-charter.html" target="_blank">IPsec</a>, a suite of protocols for securing Internet Protocol communications by authenticating and encrypting each IP packet of a data stream.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/27/monitor-an-ipsec-vpn-tunnel-on-openbsd-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>op5 Monitor tutorial part 1</title>
		<link>http://www.it-slav.net/blogs/2009/04/23/op5-monitor-tutorial-part-1/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/23/op5-monitor-tutorial-part-1/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 07:37:01 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Nagios]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Monitor]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=991</guid>
		<description><![CDATA[A demo of the benefits with op5 Monitor and what you can monitor with this Nagios based network monitoring tool. This first part gives a short introduction and overview of the tool.




]]></description>
			<content:encoded><![CDATA[<p>A demo of the benefits with <a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor</a> and what you can monitor with this Nagios based network monitoring tool. This first part gives a short introduction and overview of the tool.</p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p>
<object width="425" height="344" data="http://www.youtube.com/v/MjvcGQsmRMU&amp;hl=sv&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/MjvcGQsmRMU&amp;hl=sv&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/23/op5-monitor-tutorial-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Teledemo: op5 Products presented by Collax</title>
		<link>http://www.it-slav.net/blogs/2009/04/21/teledemo-op5-products-presented-by-collax/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/21/teledemo-op5-products-presented-by-collax/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 12:05:18 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Hints]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[op5]]></category>
		<category><![CDATA[op5 Logserver]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[op5 Statistics]]></category>
		<category><![CDATA[Collax]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=982</guid>
		<description><![CDATA[I will be running a demo of op5 products at thursday April 23:th 16:00 CET.
The demo is hosted by Collax a op5 partner in Germany.

If you want to attend, register at:
http://www.collax.com/de/ueber-collax/events-collax-live/webcast-collax-monitoring-solution.html
]]></description>
			<content:encoded><![CDATA[<p>I will be running a demo of op5 products at thursday April 23:th 16:00 CET.</p>
<p>The demo is hosted by <a href="http://www.collax.com">Collax</a> a op5 partner in Germany.</p>
<p><br class="spacer_" /></p>
<p>If you want to attend, register at:</p>
<p><a href="http://www.collax.com/de/ueber-collax/events-collax-live/webcast-collax-monitoring-solution.html" target="_blank">http://www.collax.com/de/ueber-collax/events-collax-live/webcast-collax-monitoring-solution.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/21/teledemo-op5-products-presented-by-collax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using a webcamera to detect motions and send an alarm to Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/04/13/using-a-webcamera-to-detect-motion-and-send-an-alarm-to-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/13/using-a-webcamera-to-detect-motion-and-send-an-alarm-to-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 20:49:05 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Cool things]]></category>
		<category><![CDATA[Geek stuff]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[webcam motion]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=958</guid>
		<description><![CDATA[Background
This article describe howto use a USB camera (also known as webcam) to detect motions and send an alarm to Nagios or op5 Monitor. It can be used in datacenters to send an alert if someone or something is moving or at home to detect if someone is in your house. I will place the [...]]]></description>
			<content:encoded><![CDATA[<h2>Background</h2>
<p>This article describe howto use a USB camera (also known as webcam) to detect motions and send an alarm to Nagios or op5 Monitor. It can be used in datacenters to send an alert if someone or something is moving or at home to detect if someone is in your house. I will place the camera just inside the door so everybody passing my front door will be filmed and an alert will be sent to me.</p>
<p>The software used:</p>
<ul>
<li><a target="_blank" href="http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome">Motion</a>, to detect movement and create a movie of the relevant time, pictures is also taken.</li>
<li><a target="_blank" href="http://www.nagios.org">Nagios</a> or <a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a> to create the alarm.</li>
</ul>
<p>The hardware used is an old Logitech webcam I found in my <a target="_blank" href="http://www.pytronix.se/">fathers</a> drawer  <img src='http://www.it-slav.net/blogs/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  Motion supports alot of different devices but must simple is to use a video4linux supported device.</p>
<p>The pre req. for this article is a working Nagios or op5 Monitor system.</p>
<p><span id="more-958"></span></p>
<h2>Installation</h2>
<p>I have an Ubuntu system where I attach the webcamera, dmesg gives me:</p>
<pre>
[634581.861029] usb 1-2: new full speed USB device using uhci_hcd and address 3
[634582.032251] usb 1-2: configuration #1 chosen from 1 choice
[634582.034125] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
[634582.034144] quickcam: Kernel:2.6.27-11-generic bus:1 class:FF subclass:FF vendor:046D product:0870
[634582.048202] quickcam: Sensor HDCS-1020 detected
[634582.050173] quickcam: Registered device: /dev/video0
</pre>
<p>&nbsp;</p>
<p>Installing motion is simple, just run:</p>
<pre>
sudo apt-get install motion</pre>
<p>I will use passive checks to let motion send in alerts to Nagios, the best way of doing that is by using NSCA, for theory refer to an earlier <a target="_blank" href="http://www.it-slav.net/blogs/?p=392">article</a>.</p>
<pre>
sudo apt-get install nsca</pre>
<p>&nbsp;</p>
<h2>Test motion</h2>
<p>The first thing to test is that motion works, for me to get it to work I needed no configuration, run:</p>
<pre>
sudo motion</pre>
<p>and dance in front of your camera.</p>
<p><object width="425" height="344" type="application/x-shockwave-flash" data="http://www.youtube.com/v/cOFMggDP46Y&amp;hl=sv&amp;fs=1"><param value="true" name="allowFullScreen" /><param value="always" name="allowscriptaccess" /><param value="http://www.youtube.com/v/cOFMggDP46Y&amp;hl=sv&amp;fs=1" name="src" /><param value="true" name="allowfullscreen" /></object></p>
<p>&nbsp;</p>
<p>Now motion should inform that it has created pictures and a movie.</p>
<p>&nbsp;</p>
<h2>Configuration</h2>
<p>Configure Nagios or op5 Monitor to accept alerts sent from motion:</p>
<pre>
# service 'Camera Motion Detection'
define service{
&nbsp;use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-service
 host_name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lala
 service_description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Camera Motion Detection
 check_command&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check_dummy!0 &quot;No motion detected&quot;
 max_check_attempts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
&nbsp;active_checks_enabled&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
&nbsp;flap_detection_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n
 contact_groups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it-slav_msn,it-slav_mail,call_it-slav
&nbsp;stalking_options&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n
 check_freshness&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
 freshness_threshold&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3600
}</pre>
<p>If nothing has been sent within an hour (3600 seconds), the state is set to OK by using freshness and check_dummy.</p>
<p>&nbsp;</p>
<p>Create /home/motion/scripts/check_camera_motion/send_nsca.cfg</p>
<pre>
encryption_method=0</pre>
<p>&nbsp;</p>
<p>Create /home/motion/scripts/check_camera_motion/passive_camera_warning</p>
<pre>
lala&nbsp;&nbsp;&nbsp; Camera Motion Detection&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; WARNING: Motion detected</pre>
<p>The separator must be TAB</p>
<p>&nbsp;</p>
<p>In /etc/motion/motion.conf, find the parameter on_event_start and change it to:</p>
<pre>
on_event_start&nbsp; cd /home/motion/scripts/check_camera&amp;&amp;send_nsca -H op5.mynet -c send_nsca.cfg &lt; passive_camera_warning</pre>
<p>And an alert will be sent to Nagios everytime motion detects a motion.</p>
<p>&nbsp;</p>
<p>Start motion with:</p>
<pre>
sudo motion
</pre>
<p>And do the dancing again, now you should have an Nagios alarm with status WARNING.</p>
<p>&nbsp;</p>
<h3>Hint</h3>
<p>A good idea could be to change the parameters <em>target_dir</em> and <em>snapshot_filename</em> to a directory where you can point apache websever, so you can use a webbrowser to browse your images and movies.</p>
<p>&nbsp;</p>
<h2>Links</h2>
<ul>
<li><a target="_blank" href="http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome">Motion</a>, the software used to detect motions</li>
<li><a href="http://www.nagios.org">Nagios</a></li>
<li><a target="_blank" href="http://www.op5.com/op5/products/monitor">op5 Monitor</a>, a supported version of Nagios</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/13/using-a-webcamera-to-detect-motion-and-send-an-alarm-to-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>MySql Performance Monitoring with Nagios or op5 Monitor</title>
		<link>http://www.it-slav.net/blogs/2009/04/06/mysql-performance-monitoring-with-nagios-or-op5-monitor/</link>
		<comments>http://www.it-slav.net/blogs/2009/04/06/mysql-performance-monitoring-with-nagios-or-op5-monitor/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 18:49:56 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=933</guid>
		<description><![CDATA[When using a database that are business critical it can be a good idea to monitor the internals. This article describe how-to monitor MySql with Nagios or op5 Monitor. In these case it runs a MythTV system but it could be almost anything.

Pre requirements
The pre requriements for this article is a working Nagios or op5 [...]]]></description>
			<content:encoded><![CDATA[<p>When using a database that are business critical it can be a good idea to monitor the internals. This article describe how-to monitor MySql with Nagios or op5 Monitor. In these case it runs a MythTV system but it could be almost anything.</p>
<p><br class="spacer_" /></p>
<h2>Pre requirements</h2>
<p>The pre requriements for this article is a working Nagios or op5 Installation and a working MySql database.</p>
<p><br class="spacer_" /></p>
<h2>Plugin</h2>
<p>The plugin used in this article is: <a href="http://www.consol.de/opensource/nagios/check-mysql-health" target="_blank">http://www.consol.de/opensource/nagios/check-mysql-health</a></p>
<p>Unfortunatly the webpage is in German only.</p>
<p><span id="more-933"></span><br class="spacer_" /></p>
<h2>Enable MySql to retrive information <br />
</h2>
<pre>mysql&gt; grant usage on *.* to 'nagios'@'op5' identified by 'XXXX-';</pre>
<p>op5 is the nagios hostname.</p>
<p><br class="spacer_" /></p>
<h2>Download the plugin, install and test<br />
</h2>
<p>Download the plugin from<a href="http://www.consol.de/fileadmin/opensource/Nagios/check_mysql_health-2.0.4.tar.gz" target="_blank"> http://www.consol.de/fileadmin/opensource/Nagios/check_mysql_health-2.0.4.tar.gz</a></p>
<p>I put it into /opt/plugins/custom/check_mysql_health at the Nagios server.</p>
<p>Test the command by running at the Nagios server:</p>
<pre>[root@op5 custom]# ./check_mysql_health -H mysqlhost --user nagios --password XXXX  --mode threads-connected
 OK - 5 client connection threads | threads_connected=5;10;20</pre>
<p>It works!!</p>
<p>To get a list of what the check_mysql_health plugin can monitor run:</p>
<pre>[root@op5 custom]# ./check_mysql_health --help</pre>
<p><br class="spacer_" /></p>
<h2>Configure Nagios or op5 Monitor</h2>
<p>I find the following parameters interesting to monitor:</p>
<ul>
<li>connection-time</li>
<li>keycache-hitrate</li>
<li>qcache-hitrate</li>
<li>tablecache-hitrate</li>
<li>threadcache-hitrate</li>
<li>tmp-disk-tables</li>
</ul>
<p><strong>checkcommands.cfg</strong></p>
<pre># command 'check_mysql_health'
 define command{
 command_name                   check_mysql_health
 command_line                   $USER1$/custom/check_mysql_health -H $HOSTADDRESS$ --user $ARG1$ -password $ARG2$ --mode $ARG3$
 }</pre>
<pre># command 'check_mysql_health_tresholds'
 define command{
 command_name                   check_mysql_health_tresholds
 command_line                   $USER1$/custom/check_mysql_health -H $HOSTADDRESS$ --user $ARG1$ -password $ARG2$ --mode $ARG3$ --warning $ARG4$ --critical $ARG5$
 }</pre>
<p><br class="spacer_" /></p>
<p>I created a servicegroup named mysql</p>
<p><strong>servicegroups.cfg</strong></p>
<pre># servicegroup 'mysql'
 define servicegroup{
 servicegroup_name              mysql
 alias                          MySQL
 }</pre>
<pre>I use the default thresholds in my servicedefinitions, but use check_mysql_health_thresholds instead if thresholds are required.<strong>
services.cfg</strong></pre>
<pre># service 'MySQL connection-time'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL connection-time
 check_command                  check_mysql_health!nagios!XXXX!connection-time
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<pre># service 'MySQL keycache-hitrate'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL keycache-hitrate
 check_command                  check_mysql_health!XXXX!keycache-hitrate
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<pre># service 'MySQL qcache-hitrate'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL qcache-hitrate
 check_command                  check_mysql_health!nagios!XXXX!qcache-hitrate
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<pre># service 'MySQL tablecache-hitrate'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL tablecache-hitrate
 check_command                  check_mysql_health!nagios!XXXX!tablecache-hitrate
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<pre># service 'MySQL threadcache-hitrate'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL threadcache-hitrate
 check_command                  check_mysql_health!nagios!XXXX!threadcache-hitrate
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<pre># service 'MySQL tmp-disk-tables'
 define service{
 use                            default-service
 host_name                      lala
 service_description            MySQL tmp-disk-tables
 check_command                  check_mysql_health!nagios!XXXX!tmp-disk-tables
 servicegroups                  mysql
 contact_groups                 it-slav_msn,it-slav_mail,call_it-slav
 }</pre>
<h2>The result</h2>
<h2><img class="aligncenter size-full wp-image-941" title="mysql" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/04/mysql.png" alt="mysql" width="803" height="162" /></h2>
<p><br class="spacer_" /></p>
<h2>Conclusions and wrap-up</h2>
<p>The default values are in many cases not sufficent, I have no database that do not get WARNING or CRITICAL when the default thresholds are used. If that is because the thresholds are not realistic or if it my applications that are badly implemented I do not know. So the databases needs tuning and the thresholds must be changed to get rid of constant errormessages.</p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<h2>Links</h2>
<ul>
<li><a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor </a></li>
<li><a href="http://www.nagios.org" target="_blank">Nagios</a></li>
<li><a href="http://www.it-slav.net/blogs/?p=819" target="_blank">Tuning MySQL</a></li>
<li>The plugin used in this article <a href="http://www.consol.de/opensource/nagios/check-mysql-health" target="_blank">check_mysql_health</a></li>
</ul>
<p><br class="spacer_" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/04/06/mysql-performance-monitoring-with-nagios-or-op5-monitor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Wordpress monitoring with Nagios or op5 Monitor using Webinject</title>
		<link>http://www.it-slav.net/blogs/2009/03/16/wordpress-monitoring-with-nagios-or-op5-monitor-using-webinject/</link>
		<comments>http://www.it-slav.net/blogs/2009/03/16/wordpress-monitoring-with-nagios-or-op5-monitor-using-webinject/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 19:18:39 +0000</pubDate>
		<dc:creator>peter</dc:creator>
				<category><![CDATA[Nagios]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[graph]]></category>
		<category><![CDATA[op5 Monitor]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[webinject]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.it-slav.net/blogs/?p=862</guid>
		<description><![CDATA[There are several ways of monitor a wordpress blog by using Nagios or op5 Monitor.
Wordpress uses the following parts to work:

Webserver frontend
PHP scripts
MySQL database backend
At least one system to run it on

I found one article describing howto monitor the Webserver and the MySQL database and even that a certain webpage contain a certain phrase. But [...]]]></description>
			<content:encoded><![CDATA[<p>There are several ways of monitor a wordpress blog by using Nagios or op5 Monitor.</p>
<p>Wordpress uses the following parts to work:</p>
<ul>
<li>Webserver frontend</li>
<li>PHP scripts</li>
<li>MySQL database backend</li>
<li>At least one system to run it on</li>
</ul>
<p>I found one <a href="http://www.linickx.com/archives/271/how-to-monitor-wordpress-with-nagios" target="_blank">article</a> describing howto monitor the Webserver and the MySQL database and even that a certain webpage contain a certain phrase. But I would like to emulate a user that clicks on some pages and graph the performance.</p>
<p>The tool I like for in-depth web monitoring is <a href="http://www.webinject.org/" target="_blank">webinject</a>. It allows scripting a simulated web user with alot of features.</p>
<p>I recommend to read the excellent <a href="http://www.op5.com/support/documentation/how-to/38-monitoring-websites-with-webinject" target="_blank">how-to</a> written by op5 support team and of cource use webinjects <a href="http://www.webinject.org/manual.html" target="_blank">reference manual</a>.</p>
<p><span id="more-862"></span></p>
<p>The testcase I&#8217;ve created looks like this:</p>
<pre>&lt;testcases repeat="1"&gt;
&lt;case
    id="1"
    description1="Startsidan www.it-slav.net/blogs"
    method="get"
    url="http://www.it-slav.net/blogs/"
    verifypositive="An It-Slave in the digital saltmine"
/&gt;
&lt;case
    id="2"
    description1="Nagios or op5 Monitor plugin for 1-wire humidity measurement"
    method="get"
    url="http://www.it-slav.net/blogs/?p=802"
    verifypositive="1-wire humidity probe"
/&gt;
&lt;case
    id="3"
    description1="op5 Monitor or Nagios plugin for 1-wire temperature measurement"
    method="get"
    url="http://www.it-slav.net/blogs/?p=115"
    verifypositive="check_1-wiretemp"
/&gt;
&lt;case
    id="4"
    description1="Wp-Admin"
    method="get"
    url="http://www.it-slav.net/blogs/wp-admin"
    verifyresponsecode="301"
/&gt;
&lt;/testcases&gt;
</pre>
<p>And when run in Nagios mode:</p>
<pre>[root@op5 webinject]# ./webinject.pl -c config.xml testcases/wordpressblog.xml
WebInject OK - All tests passed successfully in 4.143 seconds |time=4.143;10;;0
</pre>
<p>In checkcommands.cfg:</p>
<pre># command 'check_webinject'
define command{
    command_name                   check_webinject
    command_line                   $USER1$/webinject/webinject.pl testcases/$ARG1$
    }

In services.cfg:</pre>
<pre># service 'Webinject Blog'
define service{
    use                            default-service
    host_name                      dull
    service_description            Webinject Blog
    check_command                  check_webinject!wordpressblog.xml
    contact_groups                 it-slav_sms,it-slav_mail,call_it-slav
    }
</pre>
<p><br class="spacer_" /></p>
<p>This is a nice pnp graph of my Webinject check:</p>
<p><img class="aligncenter size-full wp-image-896" title="dull_webinject_blog" src="http://www.it-slav.net/blogs/wp-content/uploads/2009/03/dull_webinject_blog.png" alt="dull_webinject_blog" width="620" height="264" /></p>
<h2>Links:</h2>
<ul>
<li><a href="http://www.webinject.org/" target="_blank">Webinject</a></li>
<li>op5 Webinject <a href="http://www.op5.com/support/documentation/how-to/38-monitoring-websites-with-webinject" target="_blank">Howto</a></li>
<li><a href="http://www.nagios.org" target="_blank">Nagios</a></li>
<li><a href="http://www.op5.com/op5/products/monitor" target="_blank">op5 Monitor</a> </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.it-slav.net/blogs/2009/03/16/wordpress-monitoring-with-nagios-or-op5-monitor-using-webinject/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
