<?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: Pausing a single forwarder? in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579498#M13344</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241806"&gt;@JRG_Jeff&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you could insert in your missing forwarder alert a lookup to whitelist the forwarder to check or to blacklist the forwarders to not check.&lt;/P&gt;&lt;P&gt;In other words, if the liste of the forwarders to check is in a lookup called parameter.csv, you could use a search like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| metasearch index=_internale
| eval host=lower(host)
| stats count BY host
| append [ | inputlookup perimeter.csv | eval host=lower(host), count=0 | fields host count ]
| stats sum(count) AS total BY host
| where total=0&lt;/LI-CODE&gt;&lt;P&gt;in this way you check only the forwarders in perimeter and to avoid an alert for in maintenance forwarder, you can temporary delete it from the lookup.&lt;/P&gt;&lt;P&gt;Otherwise, you could create a blacklist lookup (called e.g. blacklisted_forwarders.csv9 and run something like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| metasearch index=_internale NOT [ | inputlookup blacklisted_forwarders.csv | fields host ]
| eval host=lower(host)
| stats count BY host
| append [ | inputlookup perimeter.csv | eval host=lower(host), count=0 | fields host count ]
| stats sum(count) AS total BY host
| where total=0&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Wed, 29 Dec 2021 15:59:47 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2021-12-29T15:59:47Z</dc:date>
    <item>
      <title>Pausing a single forwarder?</title>
      <link>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579496#M13343</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;I have a server that will be down for sometime, and I would like to not be inundated with "missing forwarder" alerts.&amp;nbsp; Is there a way to "pause" that alert for just that server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 29 Dec 2021 15:53:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579496#M13343</guid>
      <dc:creator>JRG_Jeff</dc:creator>
      <dc:date>2021-12-29T15:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Pausing a single forwarder?</title>
      <link>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579498#M13344</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241806"&gt;@JRG_Jeff&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you could insert in your missing forwarder alert a lookup to whitelist the forwarder to check or to blacklist the forwarders to not check.&lt;/P&gt;&lt;P&gt;In other words, if the liste of the forwarders to check is in a lookup called parameter.csv, you could use a search like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| metasearch index=_internale
| eval host=lower(host)
| stats count BY host
| append [ | inputlookup perimeter.csv | eval host=lower(host), count=0 | fields host count ]
| stats sum(count) AS total BY host
| where total=0&lt;/LI-CODE&gt;&lt;P&gt;in this way you check only the forwarders in perimeter and to avoid an alert for in maintenance forwarder, you can temporary delete it from the lookup.&lt;/P&gt;&lt;P&gt;Otherwise, you could create a blacklist lookup (called e.g. blacklisted_forwarders.csv9 and run something like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| metasearch index=_internale NOT [ | inputlookup blacklisted_forwarders.csv | fields host ]
| eval host=lower(host)
| stats count BY host
| append [ | inputlookup perimeter.csv | eval host=lower(host), count=0 | fields host count ]
| stats sum(count) AS total BY host
| where total=0&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 29 Dec 2021 15:59:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579498#M13344</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2021-12-29T15:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: Pausing a single forwarder?</title>
      <link>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579500#M13345</link>
      <description>&lt;P&gt;There is no built-in way to do that with core Splunk.&amp;nbsp; You have to modify the alert to ignore the forwarder.&amp;nbsp; When maintenance is over, remember to revert the alert.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Consider having the alert consult a lookup file of servers to ignore.&amp;nbsp; Then you just have to update the file when a server is going to be unavailable.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Dec 2021 16:01:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Pausing-a-single-forwarder/m-p/579500#M13345</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-12-29T16:01:56Z</dc:date>
    </item>
  </channel>
</rss>

