<?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 Print Monitoring Linux in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Print-Monitoring-Linux/m-p/415166#M14830</link>
    <description>&lt;P&gt;So we recently had a requirement to start monitoring Printers usage from our print server. &lt;/P&gt;

&lt;P&gt;So I was reviewing the information on &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorWindowsprinterinformation"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorWindowsprinterinformation&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;But&lt;/STRONG&gt; our Splunk Enterprise server is &lt;EM&gt;Linux&lt;/EM&gt; based. Does this mean we're out of luck? Or is there a more complicated way to accomplish the same goal? &lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2019 15:17:44 GMT</pubDate>
    <dc:creator>mwinchester</dc:creator>
    <dc:date>2019-07-26T15:17:44Z</dc:date>
    <item>
      <title>Print Monitoring Linux</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Print-Monitoring-Linux/m-p/415166#M14830</link>
      <description>&lt;P&gt;So we recently had a requirement to start monitoring Printers usage from our print server. &lt;/P&gt;

&lt;P&gt;So I was reviewing the information on &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorWindowsprinterinformation"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/MonitorWindowsprinterinformation&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;But&lt;/STRONG&gt; our Splunk Enterprise server is &lt;EM&gt;Linux&lt;/EM&gt; based. Does this mean we're out of luck? Or is there a more complicated way to accomplish the same goal? &lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2019 15:17:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Print-Monitoring-Linux/m-p/415166#M14830</guid>
      <dc:creator>mwinchester</dc:creator>
      <dc:date>2019-07-26T15:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: Print Monitoring Linux</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Print-Monitoring-Linux/m-p/415167#M14831</link>
      <description>&lt;P&gt;You can use the universal forwarder. The docs are somewhat confusing, but the line that says "Both full instances of Splunk Enterprise and universal forwarders support local collection of printer subsystem information. If you have Splunk Cloud and want to monitor printer subsystem information, use the universal forwarder to consume the information and forward it to your Splunk Cloud deployment." Splunk Cloud is Linux based, so there's no reason you can't install the UF and send data to your Linux based indexers.&lt;/P&gt;

&lt;P&gt;I sent a comment to the doc team to clarify the documentation.&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jul 2019 14:29:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Print-Monitoring-Linux/m-p/415167#M14831</guid>
      <dc:creator>vliggio</dc:creator>
      <dc:date>2019-07-27T14:29:11Z</dc:date>
    </item>
  </channel>
</rss>

