<?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 Splunk ingesting MSMQ Message in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32053#M178148</link>
    <description>&lt;P&gt;I have a legacy logging application that sends its messages to a MSMQ queue.  Can splunk be configured to read data directly from the queue?  Or do i need to write a listener application that reads the data and sends the message to Splunk via TCP?&lt;/P&gt;</description>
    <pubDate>Fri, 10 Aug 2012 15:04:31 GMT</pubDate>
    <dc:creator>rick_harrison</dc:creator>
    <dc:date>2012-08-10T15:04:31Z</dc:date>
    <item>
      <title>Splunk ingesting MSMQ Message</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32053#M178148</link>
      <description>&lt;P&gt;I have a legacy logging application that sends its messages to a MSMQ queue.  Can splunk be configured to read data directly from the queue?  Or do i need to write a listener application that reads the data and sends the message to Splunk via TCP?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2012 15:04:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32053#M178148</guid>
      <dc:creator>rick_harrison</dc:creator>
      <dc:date>2012-08-10T15:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ingesting MSMQ Message</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32054#M178149</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;You can't read the MSMQ natively (it's not in the right format). You'll have to write a wrapper that either ports it to another TCP port and read it from there are write up a .net/vbscript and do a scripted input from there.&lt;/P&gt;

&lt;P&gt;~Kate&lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2012 20:48:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32054#M178149</guid>
      <dc:creator>Kate_Lawrence-G</dc:creator>
      <dc:date>2012-08-10T20:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ingesting MSMQ Message</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32055#M178150</link>
      <description>&lt;P&gt;Have you guys done any scripts in this sense? Is it working? I have a case in which we will try to collect MSMQ information to monitor queues in Splunk...any hint on that? I will appreciate any help in this matter, thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 03 Aug 2013 20:59:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32055#M178150</guid>
      <dc:creator>wagnerbianchi</dc:creator>
      <dc:date>2013-08-03T20:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk ingesting MSMQ Message</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32056#M178151</link>
      <description>&lt;P&gt;There is a &lt;A href="http://apps.splunk.com/app/1574/"&gt;modular input for MSMQ&lt;/A&gt; that can consume the messages. It also has support for writing your own plug-ins (refer to &lt;A href="https://gist.github.com/nczeczulin/6128867"&gt;IMessageHandler.cs&lt;/A&gt;, and &lt;A href="https://gist.github.com/nczeczulin/6129089"&gt;ExampleHandlerTemplate.cs&lt;/A&gt;) to deserialize the body data before emitting to Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2014 11:11:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-ingesting-MSMQ-Message/m-p/32056#M178151</guid>
      <dc:creator>nczeczulin_splu</dc:creator>
      <dc:date>2014-02-20T11:11:16Z</dc:date>
    </item>
  </channel>
</rss>

