Threshold monitoring PostilionSystemsOverview using Not Exists for WHERE clasue

[Tristan_Barrett]

I'm in the process of building a threshold to monitor the PostilionSystemsOverview data view to check for the absence of a matching record. So I built my WHERE clause in a display, confirmed that it showed what I wanted to monitor for (the absence of), then copied the WHERE clause over to a new threshold and ticked the Not Exists box.

Then I tried to start the threshold and got the below error:

INVALID NOTEXIST SPECIFIED... \PROGNOSIS.SrcNodeMon 'MSG: 1 ASSOC'
Field substitution is not a valid action for a where clause when NOTEXIST
is specified. No record data (i.e. row of data matched by a where clause)
is returned when a NOTEXIST clause is specified.

The WHERE clause that I am trying to check for a Not Exist on is:
(SRCNODE ="ATMAppSrc5" AND ACTVCONN>0 AND STATCOND=0)

I've gone through the Help files and checked and rechecked the logic of the clause and I can't find anything wrong, so either I'm missing some simple (probable) or I've got a pickle of a problem.

[Anon]

Hi Tristan,

Thanks for posting the question.

It appears to me that the issue is probably not with the where clause; rather it's an issue with the event text (or alert message) that you are attempting to log when the threshold triggers. Under circumstances where you are using 'NOTEXIST', you are telling the threshold to alert when there is no data that matches the where clause. As there is no data, there's nothing that can be substituted into the event/alert text.

Perhaps you can check for any field substitutions in your text (noted with a @RECORD.FIELD syntax) and remove that - and then see if the threshold will start.

Cheers,
Mick Dean

[Tristan_Barrett]

It would have been something simple, I hadn't even thought to look at the destinations.

Tidied them up and problem solved, thanks for the assistance and prompt reply.

[Anon]

No problem at all. Glad we could get you up and running quickly!