<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Filter events based on event data in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/filter-events-based-on-event-data/m-p/3941268#M25472</link>
    <description>We have a production ProLiant Windows cluster that actually has three instances of an application.  One of those three is true production, and the other two are testing and training.  The testing and training instances (and thus their associated cluster resources) are often deliberately down.&lt;BR /&gt;&lt;BR /&gt;Our problem is that this always places the cluster into a degraded state, so we get alerted in SIM about it.  We ideally would like to be told when the production resources are down, but not the others.  Is there a way to filter at this level?  We don't see how to set up a filter in Automatic Actions to act based on the details of the event.  Is there a better way to handle this particular scenario?  (Knowing the general filtering answer is more useful than avoiding the issue, of course.)</description>
    <pubDate>Thu, 08 Feb 2007 14:31:18 GMT</pubDate>
    <dc:creator>Brian Drab</dc:creator>
    <dc:date>2007-02-08T14:31:18Z</dc:date>
    <item>
      <title>Filter events based on event data</title>
      <link>https://community.hpe.com/t5/server-management-systems/filter-events-based-on-event-data/m-p/3941268#M25472</link>
      <description>We have a production ProLiant Windows cluster that actually has three instances of an application.  One of those three is true production, and the other two are testing and training.  The testing and training instances (and thus their associated cluster resources) are often deliberately down.&lt;BR /&gt;&lt;BR /&gt;Our problem is that this always places the cluster into a degraded state, so we get alerted in SIM about it.  We ideally would like to be told when the production resources are down, but not the others.  Is there a way to filter at this level?  We don't see how to set up a filter in Automatic Actions to act based on the details of the event.  Is there a better way to handle this particular scenario?  (Knowing the general filtering answer is more useful than avoiding the issue, of course.)</description>
      <pubDate>Thu, 08 Feb 2007 14:31:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/filter-events-based-on-event-data/m-p/3941268#M25472</guid>
      <dc:creator>Brian Drab</dc:creator>
      <dc:date>2007-02-08T14:31:18Z</dc:date>
    </item>
  </channel>
</rss>

