Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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: 267 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
23:22, 22 Jun 2016