<?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 Re: SCOM Plug-in Module in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65996#M70528</link>
    <description>&lt;P&gt;I recently implemented this and it worked as expected.  I might make some further enhancements to include the Management Pack that the rule or monitor lives in that generated the event or alert in the first place.  We like to see that info as well.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Dec 2010 11:49:56 GMT</pubDate>
    <dc:creator>PaulEscher</dc:creator>
    <dc:date>2010-12-17T11:49:56Z</dc:date>
    <item>
      <title>SCOM Plug-in Module</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65994#M70526</link>
      <description>&lt;P&gt;We are looking at the SCOM plug-in module and the question has come up reguarding RMS vs. ACS databases.&lt;/P&gt;

&lt;P&gt;Does anyone know if the SCOM plug-in pulls data from the RMS database or the ACS database?&lt;/P&gt;

&lt;P&gt;Thank you,
Adam Puleo&lt;/P&gt;</description>
      <pubDate>Thu, 07 Oct 2010 07:30:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65994#M70526</guid>
      <dc:creator>e130199</dc:creator>
      <dc:date>2010-10-07T07:30:33Z</dc:date>
    </item>
    <item>
      <title>Re: SCOM Plug-in Module</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65995#M70527</link>
      <description>&lt;P&gt;The plugin was written to pull data from the RMS database via a Powershell snap-in included in the SCOM RMS.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Oct 2010 03:26:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65995#M70527</guid>
      <dc:creator>Leo</dc:creator>
      <dc:date>2010-10-08T03:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: SCOM Plug-in Module</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65996#M70528</link>
      <description>&lt;P&gt;I recently implemented this and it worked as expected.  I might make some further enhancements to include the Management Pack that the rule or monitor lives in that generated the event or alert in the first place.  We like to see that info as well.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Dec 2010 11:49:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/SCOM-Plug-in-Module/m-p/65996#M70528</guid>
      <dc:creator>PaulEscher</dc:creator>
      <dc:date>2010-12-17T11:49:56Z</dc:date>
    </item>
  </channel>
</rss>

