Now this works perfectly when running via powershell, when operating it via programming notification test, programming logs arise with “Status sending EXE:Ok”. The trick seems programmers be that programming PRTG notification atmosphere does not enclose each passed variable in single quotes, so items with spaces in them break programming script. It now looks as if here’s what works for us, and yes more can be added, but at the moment we don’t want programming extra info, we just need programmers know anything has happenedIn programming prtg notification settings programming variables under EXE action need programmers be specified as follows in programming parameter fieldPRTG Guys,I don’t be mindful why you do not bring desktop technological know-how simple integration programmers REST API’sit does not require that much and they are all programming same json based API’sIntegration with PagerDuty, OpsGenie, and VictorOps native WebAPI calls could be a superb function. It appears like desktop science majority of PRTG’s competitors have exiting integration with these items. It can be computer technology good sales characteristic, and also positive programmers programming pre existing userbase. If anyone is still searching for computing device science determination for this, I was able programmers conquer programming headers.