<?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: How do you request customer_identifier_all_forwarder_outputs.zip? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137958#M28378</link>
    <description>&lt;P&gt;You can redownload your forwarder credentials by doing step 2 listed here: &lt;A href="http://answers.splunk.com/answers/214420/how-do-i-setup-a-splunk-cloud-trial-sandbox-forwar.html#answer-214421"&gt;http://answers.splunk.com/answers/214420/how-do-i-setup-a-splunk-cloud-trial-sandbox-forwar.html#answer-214421&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See the writeup on the proper outputs.conf.  Note its not the same as the login URL.&lt;/P&gt;</description>
    <pubDate>Sat, 14 Feb 2015 17:41:23 GMT</pubDate>
    <dc:creator>khourihan_splun</dc:creator>
    <dc:date>2015-02-14T17:41:23Z</dc:date>
    <item>
      <title>How do you request customer_identifier_all_forwarder_outputs.zip?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137957#M28377</link>
      <description>&lt;P&gt;Does anyone know how to re-trigger the "Welcome to Splunk!" e-mail referenced in this documentation?&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/SplunkCloud/latest/Articles/GetStartedwithSplunkCloud"&gt;http://docs.splunk.com/Documentation/SplunkCloud/latest/Articles/GetStartedwithSplunkCloud&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;My cloud node lets me download and install the credentials .spl, but I don't have any endpoints information. If I point my forwarder at the same hostname that I was given for Splunk Cloud URL I just get "TcpOutputProc - Cooked connection to ip=RESOLVED_IP:9997 timed out," so it looks like I do need a different endpoint for forwarder configuration.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Feb 2015 17:36:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137957#M28377</guid>
      <dc:creator>fsalamo</dc:creator>
      <dc:date>2015-02-14T17:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: How do you request customer_identifier_all_forwarder_outputs.zip?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137958#M28378</link>
      <description>&lt;P&gt;You can redownload your forwarder credentials by doing step 2 listed here: &lt;A href="http://answers.splunk.com/answers/214420/how-do-i-setup-a-splunk-cloud-trial-sandbox-forwar.html#answer-214421"&gt;http://answers.splunk.com/answers/214420/how-do-i-setup-a-splunk-cloud-trial-sandbox-forwar.html#answer-214421&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See the writeup on the proper outputs.conf.  Note its not the same as the login URL.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Feb 2015 17:41:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137958#M28378</guid>
      <dc:creator>khourihan_splun</dc:creator>
      <dc:date>2015-02-14T17:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: How do you request customer_identifier_all_forwarder_outputs.zip?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137959#M28379</link>
      <description>&lt;P&gt;Thanks! All set.&lt;/P&gt;</description>
      <pubDate>Sat, 14 Feb 2015 19:45:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-you-request-customer-identifier-all-forwarder-outputs-zip/m-p/137959#M28379</guid>
      <dc:creator>fsalamo</dc:creator>
      <dc:date>2015-02-14T19:45:38Z</dc:date>
    </item>
  </channel>
</rss>

