Just a quick note that you that you are casting %sensorid as an [int] which is causing the script to fail as it's trying to use it as a string.

Changing the parameter from:

param(
    [string]$sensor,
    [int]$sensorid,     <----------- this here
    [string]$status,
    [string]$message,
    [string]$device,
    [string]$since,
    [string]$lastup,
    [string]$sensorURL,
    [string]$deviceURL,
    [string]$serviceURL
)

to this:

param(
    [string]$sensor,
    [string]$sensorid,     <----------- this here
    [string]$status,
    [string]$message,
    [string]$device,
    [string]$since,
    [string]$lastup,
    [string]$sensorURL,
    [string]$deviceURL,
    [string]$serviceURL
)

Once changed it worked beautifully!

Hi mhouston100,

You're right, thanks for reporting that one. Fixed :)

Kind regards
Stephan Linke, Tech Support Team

Heads up - you are missing some quotes around the variable '%sensorid' in the parameter example. This was causing the notification to fail.

Thanks Dave, I've updated the post accordingly :)

Kind regards
, Stephan Linke, Tech Support Team

Is there any way to add the Probe name to these notifications? As we have many remote sites with a Probe for each, we receive alerts like this; "Probe Health (Probe Health) on Probe Device is in a Down state!"

Sorry if questions like these are not allowed here - thanks!

Hi Pigle,

The probe name can sure be included. The easiest way would be to use -device '[%probe] %device' in the parameter field instead of just -device '%device' :)

Kind regards,
Stephan Linke, Tech Support Team

Thank you for this! It's working in our Teams, but when I get the push notification on my phone the text just says "card". What do I change to make the notification text the $title?

Could you post your parameters for the notification, please? And maybe a screenshot of the notification and the teams message itself :)

Kind regards,
Stephan Linke, Tech Support Team

Hi Stephan, This is the push notification Alan is referring to - it does not present the device. Would be handy if it did.. https://ibb.co/k4TWRm

As far as I know, you cannot distinct between different devices when triggering notifications. Probably something Microsoft has to change? It probably simply has to do with the type of message I'm using here. Just using text instead of the card may work here?

Kind regards
Stephan Linke, Tech Support Team

It worked perfectly on our environment, the only thing I haven´t been able to acomplish is to get the same Buttons (sensor, device, service, aknowledge) included into the teams mobile app, I can only get the message of the sensor in MS Teams for Android.

Kind Regards!

I'll check that tomorrow and let you know the outcome :)

@arestrepo
I've tested it with the latest iOS version of Teams (1.077.2018053001) and iOS 11.4 (15F79):



Make sure that the URLs posted to the webhook are actually valid and available publicly. Otherwise, they won't appear.

Kind regards,
Stephan Linke, Tech Support Team

Thank you, I have Checked the URLs and they seemed fine, I ve checked again the Android Teams Notification and it seems like the details window and the buttons were hidden to the right side of the Card, I´ve scrolled the card leftward and it showed me both, details and buttons.

Thank you for your help Stephan!

Just as an FYI, the current PRTG Preview 18.2.42.1618 now has native Teams notifications with the same features and more verbose information :)

Kind regards,
Stephan Linke, Tech Support Team

Is the alert acknowledgement credited to the user defined in the script or will PRTG prompt for a login if the user is not already logged into the PRTG server console?

The former one. But with the latest stable (being available next week), PRTG will feature native Teams notifications, so you might want to use that instead :)

Kind regards,
Stephan Linke, Tech Support Team

Hello,

I've configured everything as per this guide. MS Teams Channel displays empty notifications like so:

on is in a state! Details Current State Message Since Last up Sensor Device Management URL

And PRTG displays the following error:

• Response not well-formed: "(param : The term 'param' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXE\PRTG-Send-MSTeams-Notification.ps1:38 char:1 + param( + ~~~~ + CategoryInfo : ObjectNotFound: (param:String) [], CommandNotFou ndException + FullyQualifiedErrorId : CommandNotFoundException 1 )" (code: PE132)*

Any suggestions?

Please use the native notifications as they're implemented in 18.x.3 and above :)

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

I'm sorry but paying thousands of dollars a year for something that can't even send a customizable notification without me having to run a powershell script is ridiculous. You guys need to implement customizable Teams and Slack alerts already, or allow json payloads from your HTTP Execute option.

Thanks for your input on the matter, most appreciated!

I just want to state that the script was there before we have had the native notification. Due to the nature of it being a script just retrieving values from PRTG, it's more customizable by nature.

With that said, what exactly would you like to see customizable about the notifications, apart from the buttons? Perhaps you could raise a Feature Request so we can see if other customers would like to see this? That'd be great.

Thanks!

With kind regards,
Stephan Linke, Technical Support Team

I would like to be able to make the alert as small as possible, down to 1 line even, and have it sent as a 'text' message into Teams as opposed to a 'card' of some kind that takes up a ton of room. I want the ability to send sleek, streamlined messages from PRTG into my chat channels. I hate that these alerts take up so much real estate and are not customizable. For instance I should be able to remove those "Acknowledge" "Scan now" 5 buttons at the bottom of every alert that comes into Teams. It's maddening. Nobody is going to use those buttons, at least not on my team, when all they do is pop up the PRTG web interface.

So this is more about having a simple variant of the notification, and a complex one? At least that's what I'm taking away from that. Make sure to put it in the feature request. The easiest way to get this right now would be to modify the $body variable and remove the $sections part. The following would basically only post a small post with a title and the ack URL, saving some space within your channel. Let me know if that suits you for the time being ;)

# ___ ___ _____ ___
#| _ \ _ \_   _/ __|
#|  _/   / | || (_ |
#|_| |_|_\ |_| \___|
#    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.1    16/10/2020 This is the short variant of the script, only posting title and Sensor URL.  
# 1.1      10/10/2017  Fixed acknowledgement URL handling
# 1.0      12/02/2016  Initial Release
#
# ------------------
# (c) 2020 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 = "Jump to the Sensor: $($sensorURL)"
}

# 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;
}

Could we have an option to change the beaviour of Acknowlegde Alarm from the native Teams notification? The automatic acknowledge indefinitely is dangerous when some of our users click a noisy alert, if we could restrict that to acknowledge for 24 hours hours would be much better

Hello, I'm afraid to tell you that this behavior cannot be changed.