<?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 Handle different search results as one by analysing the percentage match in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444899#M126177</link>
    <description>&lt;P&gt;Hi Community,&lt;/P&gt;

&lt;P&gt;i have a search which shows me all PHP-Errors in the configured timespan. Now i want so sort this results by matching diffs other results in percent and show results over X% matching results as one.&lt;/P&gt;

&lt;P&gt;For instance:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Search Query:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=php source="/var/log/docker/php-fpm/error.log" "PHP Fatal error"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Example result 1:&lt;/EM&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[13-Aug-2019 03:01:29 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in 
/usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:22
Stack trace:
#0 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfiguration.php(10): require_once()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Example result 2:&lt;/EM&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[12-Aug-2019 17:01:01 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:12
Stack trace:
#0 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/EnvironmentPilot.php(41): include()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Field extractions are very useful but the most php-fpm-errors are very different in their appearance.&lt;/P&gt;

&lt;P&gt;Now i want a output like this instead of two results :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in 
 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:22
....
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks in advance for checking my question!&lt;/P&gt;</description>
    <pubDate>Tue, 13 Aug 2019 08:47:32 GMT</pubDate>
    <dc:creator>mmsbswe</dc:creator>
    <dc:date>2019-08-13T08:47:32Z</dc:date>
    <item>
      <title>Handle different search results as one by analysing the percentage match</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444899#M126177</link>
      <description>&lt;P&gt;Hi Community,&lt;/P&gt;

&lt;P&gt;i have a search which shows me all PHP-Errors in the configured timespan. Now i want so sort this results by matching diffs other results in percent and show results over X% matching results as one.&lt;/P&gt;

&lt;P&gt;For instance:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Search Query:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=php source="/var/log/docker/php-fpm/error.log" "PHP Fatal error"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Example result 1:&lt;/EM&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[13-Aug-2019 03:01:29 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in 
/usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:22
Stack trace:
#0 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfiguration.php(10): require_once()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;Example result 2:&lt;/EM&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[12-Aug-2019 17:01:01 Europe/Berlin] PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:12
Stack trace:
#0 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/EnvironmentPilot.php(41): include()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Field extractions are very useful but the most php-fpm-errors are very different in their appearance.&lt;/P&gt;

&lt;P&gt;Now i want a output like this instead of two results :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;PHP Fatal error:  Uncaught Error: Call to a member function fetch_assoc() on boolean in 
 /usr/share/nginx/current/typo3-web/web/typo3conf/AdditionalConfigurations/overrideSettings.php:22
....
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks in advance for checking my question!&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 08:47:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444899#M126177</guid>
      <dc:creator>mmsbswe</dc:creator>
      <dc:date>2019-08-13T08:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: Handle different search results as one by analysing the percentage match</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444900#M126178</link>
      <description>&lt;P&gt;so you extract using a rgeex from PHP Fatal error:  Uncaught Error: to end of line or to just before  Stack trace: is encountered in the log.&lt;BR /&gt;
Then you look at how many distinct such extractions you get and calculate percentages based on the counts.&lt;BR /&gt;
Is this what you are looking for?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 10:46:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444900#M126178</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2019-08-13T10:46:52Z</dc:date>
    </item>
    <item>
      <title>Re: Handle different search results as one by analysing the percentage match</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444901#M126179</link>
      <description>&lt;P&gt;Hi, i will try it. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 08:37:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Handle-different-search-results-as-one-by-analysing-the/m-p/444901#M126179</guid>
      <dc:creator>mmsbswe</dc:creator>
      <dc:date>2019-08-14T08:37:55Z</dc:date>
    </item>
  </channel>
</rss>

