<?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 What are the main risks one should consider when deploying Splunk? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96619#M3565</link>
    <description>&lt;P&gt;Basically what to look out for when deploying splunk in all areas,  resolved and unresolved issues&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 24 Oct 2011 01:59:41 GMT</pubDate>
    <dc:creator>Dark_Ichigo</dc:creator>
    <dc:date>2011-10-24T01:59:41Z</dc:date>
    <item>
      <title>What are the main risks one should consider when deploying Splunk?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96619#M3565</link>
      <description>&lt;P&gt;Basically what to look out for when deploying splunk in all areas,  resolved and unresolved issues&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2011 01:59:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96619#M3565</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2011-10-24T01:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: What are the main risks one should consider when deploying Splunk?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96620#M3566</link>
      <description>&lt;P&gt;This is really more of a discussion topic than an actual question. Definitely something more suited to the IRC channel!&lt;BR /&gt;
That said however, I will provide some URL's to Docu/Wiki pages that help to build a bigger picture. It should be stressed that deployments can vary massively and its quite hard to cover all bases before going in. Not to mention if you are after system specific issues it needs to be remembered that Splunk operates across alot of different network / hardware configurations and it's unlikely that you'll get a coherent response that is useful to yourself.&lt;/P&gt;

&lt;P&gt;Different parts of a deployment;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Installation/ComponentsofaSplunkdeployment"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Installation/ComponentsofaSplunkdeployment&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Some best practices and good links to other resources;&lt;BR /&gt;
&lt;A href="http://www.splunk.com/wiki/Deploy"&gt;http://www.splunk.com/wiki/Deploy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;How much space do you need?&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Installation/HowHowmuchspaceyouwillneed"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Installation/HowHowmuchspaceyouwillneed&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Following on from above, Licensing;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/HowSplunklicensingworks"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/HowSplunklicensingworks&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Again from above, hardware capacity;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Installation/CapacityplanningforalargerSplunkdeployment"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Installation/CapacityplanningforalargerSplunkdeployment&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Considerations for deployment data inputs;&lt;BR /&gt;
&lt;A href="http://www.splunk.com/wiki/Community:Deployment_Considerations"&gt;http://www.splunk.com/wiki/Community:Deployment_Considerations&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Backup Policy;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Whatyoucanbackup"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Whatyoucanbackup&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Data retention policy;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Do you need a hardened install? (Security requirements)&lt;BR /&gt;
&lt;A href="http://www.splunk.com/wiki/Community:DeployHardenedSplunk"&gt;http://www.splunk.com/wiki/Community:DeployHardenedSplunk&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;That said, the floor is obviously open to anyone with some good issues &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2011 08:40:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96620#M3566</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2011-10-24T08:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: What are the main risks one should consider when deploying Splunk?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96621#M3567</link>
      <description>&lt;P&gt;I would also like to add that take the time to size Splunk and make the effort to try and understand your data and what indexes you will need.  &lt;/P&gt;

&lt;P&gt;Doing this up front and now will pay off in the long run with a well oiled Splunk installation.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2011 15:09:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-are-the-main-risks-one-should-consider-when-deploying/m-p/96621#M3567</guid>
      <dc:creator>kdenton</dc:creator>
      <dc:date>2011-10-26T15:09:59Z</dc:date>
    </item>
  </channel>
</rss>

