Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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,985 Votes: 0 Revisions: 4

Overview

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.

Environment

All Orion Core versions

Cause 

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

Resolution

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

Tags

Classifications

Public