<?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: What is [accepted_keys] in transforms.conf? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58363#M11477</link>
    <description>&lt;P&gt;According to &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Transformsconf" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Transformsconf&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;[accepted_keys]&lt;/P&gt;

&lt;P&gt;&lt;NAME&gt; = &lt;KEY&gt;&lt;/KEY&gt;&lt;/NAME&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Modifies Splunk's list of key names it considers valid when automatically
checking your transforms for use of undocumented SOURCE_KEY or DEST_KEY
values in index-time transformations.&lt;/LI&gt;
&lt;LI&gt;By adding entries to [accepted_keys], you can tell Splunk that a key that is
not documented is a key you intend to work for reasons that are valid in your
environment / app / etc.&lt;/LI&gt;
&lt;LI&gt;The 'name' element is simply used to disambiguate entries, similar to -class
entries in props.conf.  The name can be anything of your chosing, including a
descriptive name for why you use the key.&lt;/LI&gt;
&lt;LI&gt;The entire stanza defaults to not being present, causing all keys not
documented just above to be flagged.&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Mon, 28 Sep 2020 14:03:49 GMT</pubDate>
    <dc:creator>splunkIT</dc:creator>
    <dc:date>2020-09-28T14:03:49Z</dc:date>
    <item>
      <title>What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58362#M11476</link>
      <description>&lt;P&gt;I noticed that in Splunk 5.0.3, &lt;CODE&gt;transforms.conf&lt;/CODE&gt; has a new section called &lt;CODE&gt;[accepted_keys]&lt;/CODE&gt;. Does anyone have an example of how this can be used?&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jun 2013 23:34:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58362#M11476</guid>
      <dc:creator>loudsong</dc:creator>
      <dc:date>2013-06-09T23:34:24Z</dc:date>
    </item>
    <item>
      <title>Re: What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58363#M11477</link>
      <description>&lt;P&gt;According to &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Transformsconf" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Admin/Transformsconf&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;[accepted_keys]&lt;/P&gt;

&lt;P&gt;&lt;NAME&gt; = &lt;KEY&gt;&lt;/KEY&gt;&lt;/NAME&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Modifies Splunk's list of key names it considers valid when automatically
checking your transforms for use of undocumented SOURCE_KEY or DEST_KEY
values in index-time transformations.&lt;/LI&gt;
&lt;LI&gt;By adding entries to [accepted_keys], you can tell Splunk that a key that is
not documented is a key you intend to work for reasons that are valid in your
environment / app / etc.&lt;/LI&gt;
&lt;LI&gt;The 'name' element is simply used to disambiguate entries, similar to -class
entries in props.conf.  The name can be anything of your chosing, including a
descriptive name for why you use the key.&lt;/LI&gt;
&lt;LI&gt;The entire stanza defaults to not being present, causing all keys not
documented just above to be flagged.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:03:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58363#M11477</guid>
      <dc:creator>splunkIT</dc:creator>
      <dc:date>2020-09-28T14:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58364#M11478</link>
      <description>&lt;P&gt;I did see that documentation. I guess I was hoping for a bit more clarity with perhaps an example on how one might put this functionality to work.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 22:05:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58364#M11478</guid>
      <dc:creator>loudsong</dc:creator>
      <dc:date>2013-06-10T22:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58365#M11479</link>
      <description>&lt;P&gt;I am adding events via the REST API, with the receivers/simple endpoint. I'm also using the Python SDK. I want to add custom metadata to a group of events in the form of index fields. Much like when I use the API I can specify the host, source, and index as http query parameters when posting the data, I want to specify arbitrary http query parameters that I want splunk to turn into index fields.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;POST ....blah/receivers/simple?source=myfile.txt&amp;amp;support_ticket=123456&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Where I want splunk to treat the support_ticket query param as an index field to be applied to all events in the POST.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 22:07:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58365#M11479</guid>
      <dc:creator>loudsong</dc:creator>
      <dc:date>2013-06-10T22:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58366#M11480</link>
      <description>&lt;P&gt;I am adding events via the rest API, with the receivers/simple endpoint. I'm also using the Python SDK. I want to add custom metadata to a group of events in the form of index fields. Much like when I use the API I can specify the host, source, and index as http query parameters when posting the data, I want to specify arbitrary http query parameters that I want splunk to turn into index fields.&lt;/P&gt;

&lt;P&gt;POST ....blah/receivers/simple?source=myfile.txt&amp;amp;support_ticket=123456&lt;/P&gt;

&lt;P&gt;Where i want splunk to treat the support_ticket query param as an index field to be applied to all events in the POST.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 22:08:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58366#M11480</guid>
      <dc:creator>loudsong</dc:creator>
      <dc:date>2013-06-10T22:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: What is [accepted_keys] in transforms.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58367#M11481</link>
      <description>&lt;P&gt;Here is an example of the [accepted_keys] usage:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/90930/upgraded-to-splunk-503-and-noticing-undocumented-key-used-in-transformsconf-messages-during-startup"&gt;http://splunk-base.splunk.com/answers/90930/upgraded-to-splunk-503-and-noticing-undocumented-key-used-in-transformsconf-messages-during-startup&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2013 22:30:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-accepted-keys-in-transforms-conf/m-p/58367#M11481</guid>
      <dc:creator>splunkIT</dc:creator>
      <dc:date>2013-06-10T22:30:30Z</dc:date>
    </item>
  </channel>
</rss>

