<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Event-Management-System on blog.monitoring-plugins.pro</title>
    <link>https://blog.monitoring-plugins.pro/tags/event-management-system/</link>
    <description>Recent content in Event-Management-System on blog.monitoring-plugins.pro</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Jun 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.monitoring-plugins.pro/tags/event-management-system/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EMS Log-Monitoring</title>
      <link>https://blog.monitoring-plugins.pro/posts/ems-log-monitoring/</link>
      <pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/ems-log-monitoring/</guid>
      <description>&lt;h2 id=&#34;how-to-integrate-the-ems-log-into-an-existing-system-monitoring-solution&#34;&gt;How to integrate the EMS-Log into an existing System-Monitoring solution&lt;/h2&gt;&#xA;&lt;p&gt;In this article &lt;em&gt;ONTAP REST APIs: Automate Notification of High-Severity Events&lt;/em&gt; Mahalakshmi describes how to use &lt;em&gt;messages&lt;/em&gt; to get notified about system &lt;em&gt;events&lt;/em&gt;, depending on their type and severity. It&amp;rsquo;s a really flexible and comprehensive way to monitor NetApps ONTAP.&lt;/p&gt;&#xA;&lt;p&gt;What if you already have a system-monitoring solution like Nagios, Icinga, op5 Monitor or Shinken in place? In that case the destinations (the recipients of the notifications) are already defined in the monitoring system. So all you need is a monitoring-plugin which does the filtering-part.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
