<?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 Development Environment (Best Practices) in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86053#M17896</link>
    <description>&lt;P&gt;Hey Guys, &lt;/P&gt;

&lt;P&gt;Trying to brainstorm on ways to create a development environment for my production splunk instance. &lt;/P&gt;

&lt;P&gt;I'm not too fluent on transforming non-native log data and would first like to test my work out in a development instance of splunk. (using free license). &lt;/P&gt;

&lt;P&gt;Just curious to see how you guys out there are doing it. &lt;/P&gt;

&lt;P&gt;I just want to make sure the data is clean and presentable before getting applied to my production indexers. &lt;/P&gt;

&lt;P&gt;Furthermore curious on how you guys out there are managing your LF between development and production. &lt;/P&gt;

&lt;P&gt;Any feedback is always much appreciated. &lt;/P&gt;

&lt;P&gt;Sorry if this sounds a little vague but the questions is pretty open ended and just looking for ideas. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
    <pubDate>Tue, 06 Mar 2012 18:53:17 GMT</pubDate>
    <dc:creator>balbano</dc:creator>
    <dc:date>2012-03-06T18:53:17Z</dc:date>
    <item>
      <title>Splunk Development Environment (Best Practices)</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86053#M17896</link>
      <description>&lt;P&gt;Hey Guys, &lt;/P&gt;

&lt;P&gt;Trying to brainstorm on ways to create a development environment for my production splunk instance. &lt;/P&gt;

&lt;P&gt;I'm not too fluent on transforming non-native log data and would first like to test my work out in a development instance of splunk. (using free license). &lt;/P&gt;

&lt;P&gt;Just curious to see how you guys out there are doing it. &lt;/P&gt;

&lt;P&gt;I just want to make sure the data is clean and presentable before getting applied to my production indexers. &lt;/P&gt;

&lt;P&gt;Furthermore curious on how you guys out there are managing your LF between development and production. &lt;/P&gt;

&lt;P&gt;Any feedback is always much appreciated. &lt;/P&gt;

&lt;P&gt;Sorry if this sounds a little vague but the questions is pretty open ended and just looking for ideas. &lt;/P&gt;

&lt;P&gt;Thanks. &lt;/P&gt;

&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2012 18:53:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86053#M17896</guid>
      <dc:creator>balbano</dc:creator>
      <dc:date>2012-03-06T18:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Development Environment (Best Practices)</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86054#M17897</link>
      <description>&lt;P&gt;This may not be best practice, but this is what I do:&lt;/P&gt;

&lt;P&gt;I have a Linux machine I use as my dev environment, but it shouldn't matter if it's windows or vmware, etc..&lt;/P&gt;

&lt;P&gt;I set up my dev environment to use the same license master as my prod environment (I have plenty of room to grow and waste space if necessary).  &lt;/P&gt;

&lt;P&gt;I also set up my prod indexers as search peers to my dev indexer:  that way if I'm developing a view or searches I can access the events in production without actually adding the views or searches to production yet.&lt;/P&gt;

&lt;P&gt;If the logs aren't already being indexed by my production instance, I usually point it to an index on my dev box and play with the data before unleashing into my production environment.&lt;/P&gt;

&lt;P&gt;You could even set up a seperate deployment server for your dev environment, or use yoru production one as well.&lt;/P&gt;

&lt;P&gt;This is just a few things I do..I'm sure there's others out there who have more ideas..&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2012 20:08:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86054#M17897</guid>
      <dc:creator>Brian_Osburn</dc:creator>
      <dc:date>2012-03-06T20:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Development Environment (Best Practices)</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86055#M17898</link>
      <description>&lt;P&gt;I especially like the search peers idea - I hadn't thought of that!&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2012 22:42:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86055#M17898</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-03-06T22:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Development Environment (Best Practices)</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86056#M17899</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Search Peers&lt;/STRONG&gt; works great - just make sure you have an enterprise license (&lt;EM&gt;this won't work with free version&lt;/EM&gt;)&lt;/P&gt;</description>
      <pubDate>Fri, 30 Nov 2012 20:53:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Development-Environment-Best-Practices/m-p/86056#M17899</guid>
      <dc:creator>slierninja</dc:creator>
      <dc:date>2012-11-30T20:53:35Z</dc:date>
    </item>
  </channel>
</rss>

