<?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: Recover all fields in a Splunk environment in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695232#M10205</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/249714"&gt;@SplunkExplorer&lt;/a&gt;&amp;nbsp;you can try this :&lt;/P&gt;&lt;PRE&gt;&amp;lt;yoursearch&amp;gt; | stats dc(*) as *&lt;/PRE&gt;</description>
    <pubDate>Mon, 05 Aug 2024 10:16:58 GMT</pubDate>
    <dc:creator>splunkreal</dc:creator>
    <dc:date>2024-08-05T10:16:58Z</dc:date>
    <item>
      <title>Recover all fields in a Splunk environment</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695229#M10204</link>
      <description>&lt;P&gt;Hi Splunkers, I have the following tasks: I need to compare 2 different Splunk instances, that should be deployed in the same way, but should be not. So I have some sub tasks, to perform this checks.&lt;/P&gt;&lt;P&gt;One of them is this: in the first instances, some fields deployed by previous Splunk admin should be present (as you can imagine, if I'm here to ask for this, no documentation has been produced). Those field should have been replicated also on the second one, migrating some apps and addon on, but some of them could be in a missing state.&lt;/P&gt;&lt;P&gt;So, the idea is: avoiding the most obvious way, whic is GUI-&amp;gt; Settings -&amp;gt; Field, is there another way to ask to Splunk: "hey, could list me all field that are inside you"'? The idea is a search, or recover them from command line, to obtain 2 file and compare them, for example 2 different txt/csv files.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2024 09:45:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695229#M10204</guid>
      <dc:creator>SplunkExplorer</dc:creator>
      <dc:date>2024-08-05T09:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: Recover all fields in a Splunk environment</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695232#M10205</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/249714"&gt;@SplunkExplorer&lt;/a&gt;&amp;nbsp;you can try this :&lt;/P&gt;&lt;PRE&gt;&amp;lt;yoursearch&amp;gt; | stats dc(*) as *&lt;/PRE&gt;</description>
      <pubDate>Mon, 05 Aug 2024 10:16:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695232#M10205</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-08-05T10:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: Recover all fields in a Splunk environment</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695246#M10206</link>
      <description>&lt;P&gt;There are two different approaches to this.&lt;/P&gt;&lt;P&gt;One is to compare the result of searches. But this is limited to a given set of constraints (source, sourcetype, host) and since props and transforms can be defined based on each of those parameters, tracking them down to the real difference in config can be tricky (and doing a summarized field count over - for example - sourcetype might not show you difference in sources).&lt;/P&gt;&lt;P&gt;Another is to run btool and compare effective configs.&lt;/P&gt;&lt;PRE&gt;splunk btool props list --debug&lt;BR /&gt;splunk btool transforms list --debug&lt;BR /&gt;splunk btool fields list --debug&lt;/PRE&gt;&lt;P&gt;and so on&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2024 12:00:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695246#M10206</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-08-05T12:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: Recover all fields in a Splunk environment</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695572#M10207</link>
      <description>&lt;P&gt;I propose the last option. But in 1st phase it could be easier to find differences without --debug option (this shows where those are defined). After you know those differences then look where those are defined.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 14:38:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Recover-all-fields-in-a-Splunk-environment/m-p/695572#M10207</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-08-07T14:38:11Z</dc:date>
    </item>
  </channel>
</rss>

