<?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 Is it possible for this search to include present errors and also dynamically add new error added by developer? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616861#M214432</link>
    <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I need help with a Splunk query. The boss wants me to have a total of all different types of errors.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I run this query:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = css-dev error = "*"&lt;/LI-CODE&gt;&lt;P&gt;it gives the logs where for each log there is an error field present. The error field has 5 values - access_denied, invalid_request, invalid_token, server_error, unauthorised_client.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to this "error" field, there are some other errors also which I want to capture but they are added by developers by adding them using log.&lt;/P&gt;&lt;P&gt;These errors are:&lt;/P&gt;&lt;P&gt;1. runtime error: attempt to get length of a boolean value&lt;/P&gt;&lt;P&gt;2. Authentication error : WRONGPASS invalid username-password pair&lt;/P&gt;&lt;P&gt;3. Error while sending 2 (size = 1KB) traces to the DD agent&lt;/P&gt;&lt;P&gt;So these above 3 errors are not included in the "error" field and so therefore when i run the query - index = css-dev error="*" , I cannot find the above 3 errors.&lt;/P&gt;&lt;P&gt;What I want is a query that should include the already present errors in the "error" field(access_denied, invalid_request, invalid_token, server_error, unauthorised_client), and should&amp;nbsp; also dynamically add any new error added by the developer.&lt;/P&gt;&lt;P&gt;Is it possible?&lt;/P&gt;</description>
    <pubDate>Wed, 12 Oct 2022 19:41:51 GMT</pubDate>
    <dc:creator>ps2019</dc:creator>
    <dc:date>2022-10-12T19:41:51Z</dc:date>
    <item>
      <title>Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616861#M214432</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I need help with a Splunk query. The boss wants me to have a total of all different types of errors.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I run this query:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index = css-dev error = "*"&lt;/LI-CODE&gt;&lt;P&gt;it gives the logs where for each log there is an error field present. The error field has 5 values - access_denied, invalid_request, invalid_token, server_error, unauthorised_client.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to this "error" field, there are some other errors also which I want to capture but they are added by developers by adding them using log.&lt;/P&gt;&lt;P&gt;These errors are:&lt;/P&gt;&lt;P&gt;1. runtime error: attempt to get length of a boolean value&lt;/P&gt;&lt;P&gt;2. Authentication error : WRONGPASS invalid username-password pair&lt;/P&gt;&lt;P&gt;3. Error while sending 2 (size = 1KB) traces to the DD agent&lt;/P&gt;&lt;P&gt;So these above 3 errors are not included in the "error" field and so therefore when i run the query - index = css-dev error="*" , I cannot find the above 3 errors.&lt;/P&gt;&lt;P&gt;What I want is a query that should include the already present errors in the "error" field(access_denied, invalid_request, invalid_token, server_error, unauthorised_client), and should&amp;nbsp; also dynamically add any new error added by the developer.&lt;/P&gt;&lt;P&gt;Is it possible?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2022 19:41:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616861#M214432</guid>
      <dc:creator>ps2019</dc:creator>
      <dc:date>2022-10-12T19:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616868#M214433</link>
      <description>&lt;P&gt;The key is making sure your search results includes the events in question. Then write a regex to extract the custom error values.&lt;/P&gt;&lt;P&gt;The regex extraction in this solution is not perfect since it's based on the incomplete data you've provided.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index="css-dev" (error=* OR error)
| rex "(?&amp;lt;custom_error&amp;gt;(\w*\s)?(E|e)rror\s?\:?(\s|\w|\-|\(|\=|\))*)"
| eval error_name=COALESCE(error, custom_error)
| where LEN(error_name)&amp;gt;1
| stats count AS event_count by error_name&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2022 20:01:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616868#M214433</guid>
      <dc:creator>johnhuang</dc:creator>
      <dc:date>2022-10-12T20:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616940#M214436</link>
      <description>&lt;P&gt;What I want is something like this:&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;error_name&amp;nbsp;&lt;/STRONG&gt;&lt;/U&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;U&gt;&lt;STRONG&gt;even&lt;/STRONG&gt;&lt;STRONG&gt;t_count&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;access_denied&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (count)&lt;/P&gt;&lt;P&gt;invalid_request&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;invalid_token&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;server_error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;unauthorised_client&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;Authorisation error :&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;runtime error:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (count)&lt;/P&gt;&lt;P&gt;xyz error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(count)&lt;/P&gt;&lt;P&gt;In future whenever any new error comes, it should then add that new error to this format with its count&lt;/P&gt;&lt;P&gt;error field has 5 values already - access_denied, invalid_request, invalid_token, server_error, unauthorised_client&lt;/P&gt;&lt;P&gt;This error field does not include the errors set by developer like - Authorisation error, runtime error, etc.&lt;/P&gt;&lt;P&gt;These errors set by developer should also be added to the list and all the errors should be under one column&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 08:54:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616940#M214436</guid>
      <dc:creator>ps2019</dc:creator>
      <dc:date>2022-10-13T08:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616942#M214437</link>
      <description>&lt;P&gt;When i run this query:&lt;/P&gt;&lt;P&gt;index="css-dev" (source != "*qa*" AND source = "*pinxtgateway*") (error=* OR error)&lt;BR /&gt;| rex "(?&amp;lt;custom_error&amp;gt;(\w*\s)?(E|e)rror\s?\:?(\s|\w|\-|\(|\=|\))*)"&lt;BR /&gt;| eval error_name=COALESCE(error, custom_error)&lt;BR /&gt;| where LEN(error_name)&amp;gt;1&lt;BR /&gt;| stats count AS event_count by error_name&lt;/P&gt;&lt;P&gt;it gives me this:&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;error_name&amp;nbsp;&lt;/STRONG&gt;&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;U&gt;&lt;STRONG&gt;event_count&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;21478&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error:&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 22&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;Server Error&amp;lt;/&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 21&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access_denied&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;1014&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;4&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;error":&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;85&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error]&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;1425919&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error ] [&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;179&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error],&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;85&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error]}"&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 170&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;invalid_request&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 22&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;invalid_token&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 4&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;open error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;179&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;server_error&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;86&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I do not want like this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 08:56:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616942#M214437</guid>
      <dc:creator>ps2019</dc:creator>
      <dc:date>2022-10-13T08:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616993#M214438</link>
      <description>&lt;P&gt;The regex error extraction needs to be improved. I'd be happy to help you with that, but you have to provide some examples of the actual data (please review to make sure there's no sensitive information).&lt;/P&gt;&lt;P&gt;You can post the results of the query here to send it to me in a message.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index="css-dev" (source != "*qa*" AND source = "*pinxtgateway*") (error=* OR error)
| rex "(?&amp;lt;custom_error&amp;gt;(\w*\s)?(E|e)rror\s?\:?(\s|\w|\-|\(|\=|\))*)"
| eval error_name=COALESCE(error, custom_error)
| search NOT error_name="*_*"
| dedup error_name
| table error_name _raw&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 14:19:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/616993#M214438</guid>
      <dc:creator>johnhuang</dc:creator>
      <dc:date>2022-10-13T14:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617034#M214439</link>
      <description>&lt;P&gt;Responding to your message. You can try one of the 2 regex below and see which ones gives you the best result. The 2nd regex extracts everything after the error, so this improves flexiblity but could give you more noise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex "[^\[](?&amp;lt;custom_error&amp;gt;(\w*\s)?(E|e)rror\s?\:?(\s|\w|\-|\(|\=|\)|\.)*)"&lt;/LI-CODE&gt;&lt;LI-CODE lang="markup"&gt;| rex "[^\[](?&amp;lt;custom_error&amp;gt;(\w*\s)?(E|e)rror.*)"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After you extract the errors, you can clean up the results further by removing unwanted details, for example:&lt;/P&gt;&lt;P&gt;Input:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Error while sending 1 (size=1024B) traces to the DD agent&lt;BR /&gt;Error while sending 1 (size=1KB) traces to the DD agent&lt;BR /&gt;Error while sending 1 (size=550B) traces to the DD agent&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rex field=custom_error mode=sed "s/\d\s\(size\=\w*\)\s//"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Output:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;Error while sending traces to the DD agent&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 18:23:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617034#M214439</guid>
      <dc:creator>johnhuang</dc:creator>
      <dc:date>2022-10-13T18:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617047#M214440</link>
      <description>&lt;P&gt;Well, you can find something but you have to know what it is. If your developers keep adding various errors in various parts of the event and in various formats - well, splunk can't guess which part is the name of the error.&lt;/P&gt;&lt;P&gt;How do you expect a solution (not even Splunk, any solution) to guess which part identifies an error from those events?&lt;/P&gt;&lt;PRE&gt;(WW) warning, (EE) error, (NI) not implemented, (??) unknown.&lt;BR /&gt;Oct 13 15:16:04.091362: whack error: Broken pipe (errno 32)&lt;BR /&gt;2022-09-24T15:31:40+0200 ERROR Error in POSTIN scriptlet in rpm package kmod-v4l2loopback-6.0.0-0.rc6.20220922gitdc164f4fb00a.43.vanilla.1.fc37.x86_64&lt;BR /&gt;2022-09-30T06:25:07+0200 INFO Error during transfer: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f37&amp;amp;arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]&lt;BR /&gt;05:45.812398 lvcreate[3460] error/errseg.c:105 Initialised segtype: error&lt;/PRE&gt;&lt;P&gt;And these are just excerpts from my laptop's logs.&lt;/P&gt;&lt;P&gt;If your logs have no common structure whatsoever and furthermore you want a general solution that includes properly extracting a field (because that's what it boils down to) in a completely undefined way... well, sorry. That can't be done.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2022 19:49:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617047#M214440</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-10-13T19:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617108#M214460</link>
      <description>&lt;P&gt;I only want that the 2 errors:&lt;/P&gt;&lt;P&gt;1. Authentication error :&lt;/P&gt;&lt;P&gt;2. runtime error:&lt;/P&gt;&lt;P&gt;also get added to the list of errors, the way of identifying them would be after error there would be a ":"(colon) present directly after the word like this - error:&lt;/P&gt;&lt;P&gt;or after a space like - error :&lt;/P&gt;&lt;P&gt;So can't we modify the regex or the query in a way so as to achieve this?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Oct 2022 09:35:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617108#M214460</guid>
      <dc:creator>ps2019</dc:creator>
      <dc:date>2022-10-14T09:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible for this search to include present errors and also dynamically add new error added by developer?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617114#M214462</link>
      <description>&lt;P&gt;This can be easily matched by something like&lt;/P&gt;&lt;PRE&gt;[Ee]rror\s*:\s*(?&amp;lt;error_message&amp;gt;.*)&lt;/PRE&gt;&lt;P&gt;But this will capture everything up to the end of the line so if you have anything allowing you to liimt the error message, not just capture any string, it would be helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Oct 2022 11:10:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-it-possible-for-this-search-to-include-present-errors-and/m-p/617114#M214462</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-10-14T11:10:05Z</dc:date>
    </item>
  </channel>
</rss>

