<?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: Alert on Local Linux Firewall Starting/Stopping - Advice For Report/Alert Output in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209571#M12059</link>
    <description>&lt;P&gt;Thanks.  That works great!  Appreciated!&lt;/P&gt;</description>
    <pubDate>Wed, 28 Dec 2016 19:09:05 GMT</pubDate>
    <dc:creator>SplunkLunk</dc:creator>
    <dc:date>2016-12-28T19:09:05Z</dc:date>
    <item>
      <title>Alert on Local Linux Firewall Starting/Stopping - Advice For Report/Alert Output</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209569#M12057</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;

&lt;P&gt;I have a query that looks for when a local firewall on my Linux systems are stopped or started.  The query looks like:&lt;/P&gt;

&lt;P&gt;index=* host=* source=/var/log/messages "starting IPv4 firewall" OR "Stopping IPv4 firewall"&lt;/P&gt;

&lt;P&gt;It works great and it catches what I'm looking for.  The process used is systemd and the output is "Starting IPv4 firewall with iptables...".  However, the output isn't in a specific field that I can drop in a table like I can with a Windows host.  Ideally I'd like to include the text Starting IPv4 . . . (or Stopping) in a table with a column heading "Status" along with the time, host name, etc..  Should I use the field extractor for the text or since the text is always static try to build that into a table somehow?  Time and host name are no problem as far as a table.  Any advice on the best way to present this in a table would be appreciated.  Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 16:27:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209569#M12057</guid>
      <dc:creator>SplunkLunk</dc:creator>
      <dc:date>2016-12-28T16:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: Alert on Local Linux Firewall Starting/Stopping - Advice For Report/Alert Output</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209570#M12058</link>
      <description>&lt;P&gt;You can use searchmatch function meanwhile to build table with your eval field.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index= host= source=/var/log/messages "starting IPv4 firewall" OR "Stopping IPv4 firewall"
| eval FirewallStatus=if(searchmatch("starting IPv4 firewall"),"Starting","Stopping")
| table _time, host, FirewallStatus 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Creating a field extraction just for identifying Status ,where such Starting/Stopping events might be of very insignificant volume compared to all the other events for the same sourcetype, might not improve any performance. Since this seems to be standard log, can you see if you have message field available on all events and whether they all can be extracted as a Message field, then you can later use eval and other transforming/extracting commands on the Message field itself. &lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 17:17:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209570#M12058</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2016-12-28T17:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: Alert on Local Linux Firewall Starting/Stopping - Advice For Report/Alert Output</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209571#M12059</link>
      <description>&lt;P&gt;Thanks.  That works great!  Appreciated!&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 19:09:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209571#M12059</guid>
      <dc:creator>SplunkLunk</dc:creator>
      <dc:date>2016-12-28T19:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: Alert on Local Linux Firewall Starting/Stopping - Advice For Report/Alert Output</title>
      <link>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209572#M12060</link>
      <description>&lt;P&gt;Is there another function that can be used to search multiple values?  For example, our RHEL6 and RHEL7 systems display different messages is the firewall is stopped/started.  So Now I want to search for "iptables has been started" OR "starting IPv4 firewall" OR "Stopping IPv4 firewall" OR "iptables has been stopped".  I want to return a status of "Starting" if either of the first two search results come back and "Stopping" if either of the second two search results come back.  Since if only accepts TRUE/FALSE it doesn't appear I can add more than two search terms.  I tried the following and got the message about only handling boolean values:&lt;/P&gt;

&lt;P&gt;index=* host=* source=/var/log/messages "Starting IPv4 firewall" OR "Stopping IPv4 firewall" OR "iptables has been started" OR "iptables has been stopped"&lt;BR /&gt;
|eval FirewallStatus=if(searchmatch("Starting IPv4 firewall" OR "iptables has been started"),"Firewall Started","Firewall Stopped")&lt;BR /&gt;
|sort -_time&lt;BR /&gt;
|convert timeformat="%a %b %d, %Y %I:%M:%S %p" ctime(_time) AS Time&lt;BR /&gt;
|Rename host AS Host, FirewallStatus AS "Firewall Status"&lt;BR /&gt;
|table Time, Host, "Firewall Status"&lt;/P&gt;

&lt;P&gt;Any help would be appreciated.  Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:45:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alert-on-Local-Linux-Firewall-Starting-Stopping-Advice-For/m-p/209572#M12060</guid>
      <dc:creator>SplunkLunk</dc:creator>
      <dc:date>2020-09-29T12:45:41Z</dc:date>
    </item>
  </channel>
</rss>

