{"id":3929,"date":"2018-12-11T14:40:27","date_gmt":"2018-12-11T19:40:27","guid":{"rendered":"http:\/\/lisa.rushworth.us\/?p=3929"},"modified":"2018-12-11T16:30:30","modified_gmt":"2018-12-11T21:30:30","slug":"splunk-posting-to-microsoft-teams-via-webhooks","status":"publish","type":"post","link":"https:\/\/www.rushworth.us\/lisa\/?p=3929","title":{"rendered":"Splunk – Posting to Microsoft Teams via Webhooks"},"content":{"rendered":"\n

Using either the default webhook action or the Teams-specific webhook<\/a>, Splunk searches can post data into Microsoft Teams. First, you need to get a webhook URL for your Teams channel. On the hamburger menu next to the channel, select “Connectors”. Select Webhook, provide a name for the webhook, and copy the webhook URL. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If you intend to use the generic webhook app, there is no need to install the Teams-specific one. The Teams-specific app gives you prettier output & a “view in splunk” button. Download the app tgz<\/a>. To install the app, go into “Manage Apps” and select “Install app from file”.
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Click ‘Browse…’ and find the tgz you downloaded. Click ‘Upload’ to install the app to Splunk.
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now create a search for which you want to post data into your Teams channel. Click “Save As” and select “Alert”
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Provide a title for the alert — you can use real-time or scheduled alerts. Once you’ve got the alert sorted, select “Add Actions” and select the Teams webhook action (or the generic webhook action if you intend to use that one). Paste in the URL from your Teams channel webhook and click “Save”.
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You”ll see a confirmation that the alert has been saved. Close this.
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now you would think<\/em> you’d be ready to use it … but wait. Neither one works out of the box. In the Splunk log, you see error 400 “Bad data” reported.
<\/p>\n\n\n\n

For the default webhook app, edit the Python script (\/opt\/splunk\/etc\/apps\/alert_webhook\/bin\/webhook.py in my case). Find the section where the JSON body is built. Teams requires a summary or title within the POST data. I just added a static summary, but you could do something fancier.
<\/p>\n\n\n\n

        body = OrderedDict(
            sid=settings.get('sid'),
            summary='LJRWebhook',
<\/strong>            search_name=settings.get('search_name'),
            app=settings.get('app'),
            owner=settings.get('owner'),
            results_link=settings.get('results_link'),
            result=settings.get('result')<\/pre>\n\n\n\n
For the Teams-specific webhook, edit the Python script (\/opt\/splunk\/etc\/apps\/alert_msteams\/bin\/teams.py in my case) and find the section where the facts list is populated. There’s too much data being sent through. There’s probably a way to filter it out in Splunk, but I don’t know how \ud83d\ude42 <\/p>\n\n\n\n
The right<\/em> way to do it is select the most important items from settings.get(‘result’).items that you want to be displayed within Teams and populate facts with those elements. I used a new list, strWantedKeys, to determine which keys should be added to the facts list. The quick\/ugly way is to just take the first n<\/em> items from the result items (settings.get(‘results’).items()[:7]<\/em><\/strong> gets seven … 8 produced a ‘bad payload received by generic incoming webhook’ error from Teams. 
<\/p>\n\n\n\n
try:<\/code>
    settings = json.loads(sys.stdin.read())<\/code>
    print >> sys.stderr, \"DEBUG Settings: %s\" % settings<\/code>
    url = settings['configuration'].get('url')<\/code>
    facts = []<\/code>
    strWantedKeys = ['sourcetype', '_raw', 'host', 'source']<\/strong><\/code>
    for key,value in settings.get('result').items():<\/code>
        if key in strWantedKeys:<\/strong><\/code>
            facts.append({\"name\":key, \"value\":value})<\/code>
    body = OrderedDict(<\/code><\/pre>\n\n\n\n
For reference, the original facts list was:
<\/p>\n\n\n\n
    \"facts\": [{\n        \"name\": \"index\",\n        \"value\": \"history\"\n    }, {\n        \"name\": \"_raw\",\n        \"value\": \"Test push to teams 555\"\n    }, {\n        \"name\": \"_eventtype_color\",\n        \"value\": \"\"\n    }, {\n        \"name\": \"host\",\n        \"value\": \"10.10.15.134:8088\"\n    }, {\n        \"name\": \"source\",\n        \"value\": \"http:Sendmail testing\"\n    }, {\n        \"name\": \"_si\",\n        \"value\": [\"49cgc3e5e52e\", \"history\"]\n    }, {\n        \"name\": \"sourcetype\",\n        \"value\": \"mysourcetype\"\n    }, {\n        \"name\": \"_indextime\",\n        \"value\": \"1544554125\"\n    }, {\n        \"name\": \"punct\",\n        \"value\": \"___\"\n    }, {\n        \"name\": \"linecount\",\n        \"value\": \"\"\n    }, {\n        \"name\": \"_time\",\n        \"value\": \"1544554125\"\n    }, {\n        \"name\": \"eventtype\",\n        \"value\": \"\"\n    }, {\n        \"name\": \"_sourcetype\",\n        \"value\": \"mysourcetype\"\n    }, {\n        \"name\": \"_kv\",\n        \"value\": \"1\"\n    }, {\n        \"name\": \"_serial\",\n        \"value\": \"15\"\n    }, {\n        \"name\": \"_confstr\",\n        \"value\": \"source::http:Sendmail testing|host::10.10.15.134:8088|mysourcetype\"\n    }, {\n        \"name\": \"splunk_server\",\n        \"value\": \"\"\n    }]<\/code><\/pre>\n\n\n\n
Now<\/strong> generate a message that matches your search — you’ll see a post created in your Teams channel.<\/p>\n\n\n\n
\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"
Using either the default webhook action or the Teams-specific webhook, Splunk searches can post data into Microsoft Teams. First, you need to get a webhook URL for your Teams channel. On the hamburger menu next to the channel, select “Connectors”. Select Webhook, provide a name for the webhook, and copy the webhook URL. If you …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[677,30],"tags":[675,666,716,717,665,718],"class_list":["post-3929","post","type-post","status-publish","format-standard","hentry","category-office-365","category-system-administration","tag-did-you-know","tag-microsoft-teams","tag-splunk","tag-splunk-enterprise","tag-teams","tag-webhook"],"_links":{"self":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/3929","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3929"}],"version-history":[{"count":2,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/3929\/revisions"}],"predecessor-version":[{"id":3940,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/3929\/revisions\/3940"}],"wp:attachment":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3929"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3929"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3929"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}