Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Post to HTTP action failure after configuring alerts

Post to HTTP action failure after configuring alerts

Created by Harry Griffiths, last modified by MindTouch on Jun 23, 2016

Views: 1,781 Votes: 0 Revisions: 4


This article addresses the issue where an action is not executed when a Windows volume triggers after configuring alerts with a POST HTTP action such as sending alert messages to SLACK API.


All Orion Core versions


This occurs when there is an invalid character in the JSON string value, such as the unescaped backslash.


Verify if you action contains ${N=SwisEntity;M=Caption}

If you have volume caption such as "C:\ Label" to be able to use it JSON it has to be "C:\\ Label"

There is currently no known way to do it. The following is a workaround to replace the SWIS caption macro with regular SQL macro using the replace function:

${SQL: SELECT replace(Caption, '\', '\\') FROM Volumes WHERE VolumeID = ${VolumeID}}



Last modified