Accepted Answer

Votes:

2

This article applies to PRTG Network Monitor 16 or later

Native Teams Notifactions in PRTG 18.3.42.1727

Starting with this version, PRTG has native Teams notifications with the same features and more verbose information :)

Sending PRTG Notifications to Microsoft Teams

Yes, this is possible! Microsoft Teams is a group chat client recently introduced. While testing it, we saw that we could push notifications to it using webhooks and PowerShell. You know what this means? Right, you can send PRTG Notifications with your very own Teams bot! Even better, you have access to the sensor, device, and service URL and can acknowledge it right from within the message.

This is how your push notifications can look like:

Requirements

Microsoft Teams installed and running.
A webhook connector for your channel (see the section Setup below).
Working PowerShell notifications. See the Paessler Knowledge Base for a Guide for installing PowerShell based sensors.

Setup

Open the Channel and click the More Options button which appears as three dots at the top right of the window.
Select Connectors.
Scroll down to Incoming Webhook and click the Add button.
Choose a name you like for the connector as well as an image and finally click Create.
A new unique URI is automatically generated. Copy this URI string into the script where it says
<insert-your-webhook-url>.
Save the script as C:\Program Files (x86)\PRTG Network Monitor\Notifications\EXE\PRTG-Send-MSTeams-Notification.ps1
Create a new notification that executes the script using the parameters below and configure it as shown:

Parameters

Parameter	Type	Description
sensor	String	The name of the sensor
sensorID	String	The ID of the sensor
status	String	The current status of the sensor
message	String	The current message of the sensor
device	String	The device of the sensor
since	String	Timestamp when the problem started
sensorURL	String	The URL of the sensor
deviceURL	String	The URL of the device
serviceURL	String	The service URL of the device

Parameter Example

-sensor '%sensor' -sensorID '%sensorid' -status '%status' -message '%message' -since '%since' -lastup '%lastup' -device '%device' -sensorURL '%linksensor' -deviceURL '%linkdevice' -serviceURL '%serviceurl'

Configuration

In the configuration area of the script, you need to configure the URL to your PRTG server and the webhook you got when you added it (see step 5 from the Setup above).

#PRTG Server
$PRTGServer = ""
$PRTGUsername = ""
$PRTGPasshash  = 123456789

# configure this URL to be your actual webhook URL
$uri = "<insert-your-webhook-url>"

Version History

Date	Version	Notes
December 2nd, 2016	1.0	Initial Release
November 10th, 2017	1.1	Fixed acknowledge link handling

Script

# ___ ___ _____ ___
#| _ \ _ \_   _/ __|
#|  _/   / | || (_ |
#|_| |_|_\ |_| \___|
#    NETWORK MONITOR
#-------------------
# Description: This notification script will send to your Microsoft Teams Channel  
# Parameters:
#    [string]$sensor        - the name of the sensor
#    [string]$sensorid      - the id of the sensor
#    [string]$status        - the status 
#    [string]$message       - the message of the sensor 
#    [string]$since         - the time since the state is like this
#    [string]$lastup        - the time the sensor was up last
#    [string]$device        - the device of the sensor
#    [string]$sensorURL     - the sensor URL so you can access it directly
#    [string]$deviceURL     - the device URL 
#    [string]$serviceURL    - the service URL
# 
# Requirements
# ------------------
# - Microsoft Teams installed and running
# - A webhook connector for your channel (see Setup)
# - Working PowerShell notifications - Guide for installing PowerShell based sensors: https://kb.paessler.com/users/my_answers/71356
# 
# Full installation guide can be found here: https://kb.paessler.com/en/topic/72306
#
# Version History
# ------------------
# Version  Date        Notes
# 1.1      10/10/2017  Fixed acknowledgement URL handling
# 1.0      12/02/2016  Initial Release
#
# ------------------
# (c) 2016 Stephan Linke | Paessler AG
param(
    [string]$sensor,
    [int]$sensorid,
    [string]$status,
    [string]$message,
    [string]$device,
    [string]$since,
    [string]$lastup,
    [string]$sensorURL,
    [string]$deviceURL,
    [string]$serviceURL
)

################
# Configuration 
################

#PRTG Server
$PRTGServer = ""
$PRTGUsername = ""
$PRTGPasshash  = 123456789

#Acknowledgement Message for alerts ack'd via Teams
$ackmessage = "Problem has been acknowledged via Teams chat."

#Directory for logging
$logDirectory = "C:\temp\prtg-notifications-msteam.log"

# configure this URL to be your actual webhook URL
$uri = "<insert-your-webhook-url>"

# the acknowledgement URL 
$ackURL = [string]::Format("{0}/api/acknowledgealarm.htm?id={1}&ackmsg={2}&username={3}&passhash={4}",$PRTGServer,$sensorID,$ackmessage,$PRTGUsername,$PRTGPasshash);

# the title of your message, different templates for not up, up and acknowledged
if($status -ne "Up")
{ $title = [string]::Format("{0} on {1} is in a {2} state!", $sensor, $device, $status) }
elseif($status -eq "Up")
{ $title = [string]::Format("{0} on {1} is up again!", $sensor, $device); $ackURL = ""; }
elseif($status -eq "Acknowledged")
{ $title = [string]::Format("The problem with {0} on {1} has been acknowledged.", $sensor, $device); $ackURL = ""; }

# accept all HTTPS certificates, necessary for the webhook 
add-type @"
    using System.Net;
    using System.Security.Cryptography.X509Certificates;
    public class TrustAllCertsPolicy : ICertificatePolicy {
        public bool CheckValidationResult(
            ServicePoint srvPoint, X509Certificate certificate,
            WebRequest request, int certificateProblem) {
            return true;
        }
    }
"@
[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy

########################

$body = ConvertTo-Json -Depth 6 @{
    title = $($title)
    text = " "
    sections = @(
        @{
            activityTitle = " "
            activitySubtitle = " "            
        },
        @{
            title = 'Details'
            facts = @(
                @{
                name = 'Current State'
                value = $($status)
                },
                @{
                name = 'Message'
                value = $($message)
                },
                @{
                name = 'Since'
                value =$($since)
                },
                @{
                name = 'Last up'
                value = $($lastup)
                },
                @{
                name = 'Sensor'
                value = $($sensorURL)
                },
                @{
                name = 'Device'
                value = $($deviceURL)
                },
                @{
                name = 'Management URL'
                value = $($serviceURL)
                }
            )
            potentialAction = @(@{
            '@context' = 'http://schema.org'
            '@type' = 'ViewAction'
            name = 'Sensor Page'
            target = @($sensorURL)
            },
            @{
            '@context' = 'http://schema.org'
            '@type' = 'ViewAction'
            name = 'Device Page'
            target = @($deviceURL)
            },
            @{
            '@context' = 'http://schema.org'
            '@type' = 'ViewAction'
            name = 'Service URL'
            target = @($serviceURL)
            },
            @{
            '@context' = 'http://schema.org'
            '@type' = 'ViewAction'
            name = 'Acknowledge Alert'
            target = @($ackURL)
            }

            )
        }
    )
 
}

# We need to encode the body with UTF8, otherwise the send might
# fail if the messages contain any characters that cannot be converted
$enc = [system.Text.Encoding]::UTF8
$encodedBody = $enc.GetBytes($body)

try 
{ Invoke-RestMethod -uri $uri -Method Post -body $encodedBody -ContentType 'application/json'; exit 0; }
Catch
{
    $ErrorMessage = $_.Exception.Message
    (Get-Date).ToString() +" - "+ $ErrorMessage | Out-File -FilePath $LogDirectory -Append
    exit 2;
}

Note: The script is provided as is and may or may not work with your installation.

If you need any further customizations for your environment, feel free to implement them. If you encounter any bugs, feel free to share them :)

Credits

Script and installation steps partially taken from Microsoft Technet.

More

PRTG Manual: How to setup notifications in PRTG
Paessler Knowledge Base: Send notifications to Slack with PRTG
Paessler Knowledge Base: Push Notifications From PRTG
Paessler Knowledge Base: FAQ for Push Notifications and the PRTG Cloud

What is this?

Top Tags

[IMPLEMENTED] Can I send notifications to Microsoft Teams with PRTG?

6

2