|angela b40e3f7a7c Fix for useless OK tickets after sensors go back up||1 month ago|
|img||5 months ago|
|CHANGELOG.md||5 months ago|
|LICENSE||5 months ago|
|README.md||5 months ago|
|ZendeskWebhook.ps1||1 month ago|
Automatically open Zendesk tickets for triggered sensors using Powershell. Forked from Integrating Zendesk and PRTG
This script solves the single quotes bug PRTG developers won't fix for Powershell EXE Notifications.
Error by lookup value
Critical (2) in channel Imaging Unit (Magenta)
.. if additional triggers from the same sensor, a newline to easily list the problems
This version has additional features:
C:\Program Files (x86)\PRTG Network Monitor\Notifications\EXE(your path may vary if using a different architecture with your PRTG server)
powershell -Device '%device' -Status '%status' -Down '%down' -Group '%group' -commentssensor '%commentssensor' -CommentsProbe '%commentsprobe' -Message ''%message''
If you'd like to add additional verbiage to your tickets, you can call additional parameters in similar fashion to the existing parameters.
(Don't forget to add them to params() to initialize inside
If you prefer to use password authentication with Zendesk instead of token auth (the default), simply remove '/token' from the username.
Tietze's release is unlicensed/public domain; my changes are licensed under GPL2