<?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: different time fields in use in _audit index in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/602928#M209845</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/246998"&gt;@jason0&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I don't know why there's this behaviour, this i a question for Splunk Project Team, but anyway, you already identified the solution: use coalesce to be sure to have a value for calculations.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2022 06:51:23 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-06-23T06:51:23Z</dc:date>
    <item>
      <title>Why do some entries (of type search) have api_et, api_lt, and others have apiStartTime,apiEndTime?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/602889#M209836</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I am digging through my _audit index to see what searches people are running over time, but I am confused by the following fields.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;api_et , api_It&lt;/LI&gt;
&lt;LI&gt;apiStartTime, apiEndTime&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;It would appear that api_et and apiEndTime are the same thing.&amp;nbsp; same with api_lt, and api_StartTime.&amp;nbsp; &amp;nbsp;I get that api_(el)t are epoch times, and the others are formatted dates.&lt;/P&gt;
&lt;P&gt;Why do some entries (of type search) have api_et, api_lt, and others have apiStartTime,apiEndTime?&amp;nbsp; Thus far I have to do any calculations based on the presence of both sets and use coalesce to choose between the one that's not bogus.&lt;/P&gt;
&lt;P&gt;--jason&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 19:00:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/602889#M209836</guid>
      <dc:creator>jason0</dc:creator>
      <dc:date>2022-06-23T19:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: different time fields in use in _audit index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/602928#M209845</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/246998"&gt;@jason0&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I don't know why there's this behaviour, this i a question for Splunk Project Team, but anyway, you already identified the solution: use coalesce to be sure to have a value for calculations.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 06:51:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/602928#M209845</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-06-23T06:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: different time fields in use in _audit index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/603179#M209916</link>
      <description>&lt;P&gt;Thanks Guiseppe, I appreciate your response.&amp;nbsp; It helps me a lot!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--jason&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 15:36:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/603179#M209916</guid>
      <dc:creator>jason0</dc:creator>
      <dc:date>2022-06-24T15:36:21Z</dc:date>
    </item>
    <item>
      <title>Re: different time fields in use in _audit index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/603180#M209917</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/246998"&gt;@jason0&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 15:39:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-do-some-entries-of-type-search-have-api-et-api-lt-and-others/m-p/603180#M209917</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-06-24T15:39:07Z</dc:date>
    </item>
  </channel>
</rss>

