<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notificationforwarder on ConSol Monitoring</title><link>https://omd.consol.de/tags/notificationforwarder/</link><description>Recent content in Notificationforwarder on ConSol Monitoring</description><generator>Hugo</generator><language>en</language><atom:link href="https://omd.consol.de/tags/notificationforwarder/index.xml" rel="self" type="application/rss+xml"/><item><title>notificationforwarder</title><link>https://omd.consol.de/docs/plugins/notificationforwarder/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://omd.consol.de/docs/plugins/notificationforwarder/</guid><description>&lt;p&gt;This framework focuses on two aspects: how to transport a notification to the recipient system and which format to use.&#10;In the beginning, Naemon or one of the other monitoring cores will execute a command line. The actual script and the individual command line parameters are defined in a command definition. Typical parameters are (I use the notation of Nagios macros) HOSTNAME, SERVICEDESC, SERVICESTATE, SERVICEOUTPUT. These snippets need to be combined into a payload suitable for the receiving system. And then this payload must be transported to it. We call the two components &lt;em&gt;formatter&lt;/em&gt; and &lt;em&gt;forwarder&lt;/em&gt;. The formatter takes the raw input data and creates a payload and the forwarder transmits the payload to the destination.&#10;What the framework does for you behind the scenes: When forwarding to a recipient fails, the event is saved in a local SQLite database for a certain time and re-sent when the script is next called and the recipient is available again. Logging of successful and of course failed deliveries is also done automatically.&lt;br&gt;&#10;There is also a component &lt;em&gt;reporter&lt;/em&gt; which will rarely be used. Its purpose is to run additional code after a successful or failed delivery.\&lt;/p&gt;</description></item></channel></rss>