<?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 Hung Job Monitoring via Logs in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Hung-Job-Monitoring-via-Logs/m-p/559857#M159085</link>
    <description>&lt;P&gt;I have a search string that details the last log entry for all running jobs [shown in ascending order] bar a few jobs [as either completed OR of little interest]...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;index=ee_rpa_uipath_platform AND OrganizationUnitID=19 | dedup RobotName | table User, RobotName, _time, Message | sort _time | search (NOT Message IN("*complete*", "*ended*") AND NOT RobotName="ALWORKER*") &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;What I now want is to reduce the returned set to logs that are over 30 mins old i.e. if the log file has NOT been updated in the past 30mins then there is a good chance that the job has hung&lt;/P&gt;&lt;P&gt;I have tried the following command...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;index=ee_rpa_uipath_platform AND OrganizationUnitID=19 | dedup RobotName | table User, RobotName, _time, Message | sort _time | search (NOT Message IN("*complete*", "*ended*") AND NOT RobotName="ALWORKER*") &lt;STRONG&gt;| where earliest=-30m@m&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;...but I receive the following error...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;"Error in 'where' command: The operator at 'm@m' is invalid."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Two questions&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What's wrong with my syntax and/or&lt;/LI&gt;&lt;LI&gt;Is there a better way to to get the oldest last log entry from a set of job log files&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Fri, 16 Jul 2021 18:05:11 GMT</pubDate>
    <dc:creator>Mick_OBrien</dc:creator>
    <dc:date>2021-07-16T18:05:11Z</dc:date>
    <item>
      <title>Hung Job Monitoring via Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Hung-Job-Monitoring-via-Logs/m-p/559857#M159085</link>
      <description>&lt;P&gt;I have a search string that details the last log entry for all running jobs [shown in ascending order] bar a few jobs [as either completed OR of little interest]...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;index=ee_rpa_uipath_platform AND OrganizationUnitID=19 | dedup RobotName | table User, RobotName, _time, Message | sort _time | search (NOT Message IN("*complete*", "*ended*") AND NOT RobotName="ALWORKER*") &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;What I now want is to reduce the returned set to logs that are over 30 mins old i.e. if the log file has NOT been updated in the past 30mins then there is a good chance that the job has hung&lt;/P&gt;&lt;P&gt;I have tried the following command...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;index=ee_rpa_uipath_platform AND OrganizationUnitID=19 | dedup RobotName | table User, RobotName, _time, Message | sort _time | search (NOT Message IN("*complete*", "*ended*") AND NOT RobotName="ALWORKER*") &lt;STRONG&gt;| where earliest=-30m@m&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;...but I receive the following error...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;"Error in 'where' command: The operator at 'm@m' is invalid."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Two questions&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What's wrong with my syntax and/or&lt;/LI&gt;&lt;LI&gt;Is there a better way to to get the oldest last log entry from a set of job log files&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 16 Jul 2021 18:05:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Hung-Job-Monitoring-via-Logs/m-p/559857#M159085</guid>
      <dc:creator>Mick_OBrien</dc:creator>
      <dc:date>2021-07-16T18:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Hung Job Monitoring via Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Hung-Job-Monitoring-via-Logs/m-p/579502#M201931</link>
      <description>&lt;P&gt;Re-visited, re-thought and re-wrote.&amp;nbsp; This seems to work...&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;&lt;FONT face="courier new,courier"&gt;index=ee_rpa_uipath_platform AND OrganizationUnitID=19 | dedup RobotName | table User, RobotName, _time, Message | sort _time | search (NOT Message IN("*complete*", "*ended*") AND NOT RobotName="ALWORKER*") &lt;FONT color="#000000"&gt;&lt;STRONG&gt;| where _time &amp;gt; relative_time(now(), "-1440m@m") AND _time &amp;lt; relative_time(now(), "-30m@m")&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;I still do not understand what was wrong with original search string syntax&lt;/P&gt;</description>
      <pubDate>Wed, 29 Dec 2021 16:19:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Hung-Job-Monitoring-via-Logs/m-p/579502#M201931</guid>
      <dc:creator>Mick_OBrien</dc:creator>
      <dc:date>2021-12-29T16:19:16Z</dc:date>
    </item>
  </channel>
</rss>

