<?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: How to send alerts to multiple emails based on lookup table match on host owners? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202381#M58700</link>
    <description>&lt;P&gt;You will need these commands:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;stats, map, and sendemail
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If you give more logic and example searches, then people will give more specific answers.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Dec 2016 22:14:11 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2016-12-19T22:14:11Z</dc:date>
    <item>
      <title>How to send alerts to multiple emails based on lookup table match on host owners?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202379#M58698</link>
      <description>&lt;P&gt;We currently have a lookup table with hosts and their respective owner email.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;host ; host owner email&lt;/STRONG&gt;&lt;BR /&gt;
ABCD1234 ; &lt;A href="mailto:ABCD1234Dist@emailadd.com"&gt;ABCD1234Dist@emailadd.com&lt;/A&gt;&lt;BR /&gt;
XYZ123 ; &lt;A href="mailto:XYZ123Dist@emailadd.com"&gt;XYZ123Dist@emailadd.com&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;We'd like to trigger email alerts if any host becomes non-compliant by the 6th day to warn the owners to remediate the issues before they get on the 7th-day non-compliant report. Given, that the two sample hosts above meet this condition, how would we incorporate this logic into the email alerting, if not through the alert wizard?&lt;/P&gt;

&lt;P&gt;Thanks for any help!&lt;BR /&gt;
Trista&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2016 21:48:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202379#M58698</guid>
      <dc:creator>tmaltizo</dc:creator>
      <dc:date>2016-12-19T21:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: How to send alerts to multiple emails based on lookup table match on host owners?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202380#M58699</link>
      <description>&lt;P&gt;I think the "sendemail" command is what you're looking for.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.1/SearchReference/Sendemail"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.1/SearchReference/Sendemail&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2016 22:03:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202380#M58699</guid>
      <dc:creator>jimodonald</dc:creator>
      <dc:date>2016-12-19T22:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to send alerts to multiple emails based on lookup table match on host owners?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202381#M58700</link>
      <description>&lt;P&gt;You will need these commands:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;stats, map, and sendemail
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If you give more logic and example searches, then people will give more specific answers.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2016 22:14:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-send-alerts-to-multiple-emails-based-on-lookup-table/m-p/202381#M58700</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-12-19T22:14:11Z</dc:date>
    </item>
  </channel>
</rss>

