<?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: Which field to store meta data about alert begin deployed in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601412#M13949</link>
    <description>&lt;P&gt;Once events have been indexed (stored) no new fields can be added.&amp;nbsp; If you need to store additional information then you have a few options:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Write it to a lookup file&lt;/LI&gt;&lt;LI&gt;Write it to the KVStore&lt;/LI&gt;&lt;LI&gt;Write it to a summary index (or a regular index)&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Fri, 10 Jun 2022 18:57:50 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2022-06-10T18:57:50Z</dc:date>
    <item>
      <title>Which field to store meta data about alert begin deployed?</title>
      <link>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601411#M13948</link>
      <description>&lt;P&gt;I want to save some meta-data (operational history of the alert (beyond the text description)) along with alert as a json object in a field.&amp;nbsp; This is from automated&amp;nbsp; pipelines using sdk (nodejs/python) and POST API&amp;nbsp; to splunk servers.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 18:59:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601411#M13948</guid>
      <dc:creator>mosh</dc:creator>
      <dc:date>2022-06-10T18:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Which field to store meta data about alert begin deployed</title>
      <link>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601412#M13949</link>
      <description>&lt;P&gt;Once events have been indexed (stored) no new fields can be added.&amp;nbsp; If you need to store additional information then you have a few options:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Write it to a lookup file&lt;/LI&gt;&lt;LI&gt;Write it to the KVStore&lt;/LI&gt;&lt;LI&gt;Write it to a summary index (or a regular index)&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 10 Jun 2022 18:57:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601412#M13949</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-06-10T18:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: Which field to store meta data about alert begin deployed?</title>
      <link>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601991#M13963</link>
      <description>&lt;P&gt;This has to part of savedsearch (alert/correlation search param), before it is deployed/updated, but should not affect splunk actions in anyway. Otherwise I can manage it myself (outside of splunk) as I do right now.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 22:10:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Which-field-to-store-meta-data-about-alert-begin-deployed/m-p/601991#M13963</guid>
      <dc:creator>mosh</dc:creator>
      <dc:date>2022-06-15T22:10:19Z</dc:date>
    </item>
  </channel>
</rss>

