Increase value of custom property

I'm attempting to create a custom property that will act as a counter.

My goal is to have it increase by one each time an alert is triggered.

Then I can use that unique value in emails to our ticketing system so delayed and reset action emails will update the tickets automatically with the new information.

I'm running into an issue when trying to use the Change Custom Property action to perform the increase.

If I use a Custom Property that is an Integer Number, it fails with the following error (note: the first '1' is actually ${N=SwisEntity;M=CustomProperties.NodeDown_Count_Node} )

If I use a custom property that is in text format the field updates to the formula, rather than a number like the below examples:

${N=SWQL;M=Select SUM(1+1)}

${N=SWQL;M=SELECT SUM(NodeDown_Count_Node+1)FROM Orion.NodesCustomPropertiesWhere NodeID = ${N=SwisEntity;M=CustomProperties.NodeID}}

I've tried looking for examples online and I realized that I'm probably missing something simple due to my lack of experience with SQL and SolarWinds that is so obvious most people wouldn't need to ask about.

Please let me know if I've explained my issue poorly and I would be happy to go into more detail.

If you could help shed some light on this issue I would appreciate it!

Find more posts tagged with

custom_properties

Automation

trigger action

Accepted answers

ecmel

I would suggest using the "Integer" type for your custom property as it will keep integer data only.

Then you should be able to set your custom property using this SWQL query variable in your "Change Custom Property" alert action:

${N=SWQL;M=SELECT abs((ISNULL(NodeDown_Count_Node,0))+1) as new_value FROM Orion.NodesCustomProperties where NodeID=${N=SwisEntity;M=NodeID} }

All comments

ecmel

I would suggest using the "Integer" type for your custom property as it will keep integer data only.

Then you should be able to set your custom property using this SWQL query variable in your "Change Custom Property" alert action:

${N=SWQL;M=SELECT abs((ISNULL(NodeDown_Count_Node,0))+1) as new_value FROM Orion.NodesCustomProperties where NodeID=${N=SwisEntity;M=NodeID} }

adam.beedell

Ecmel is correct, but to add context - It's saving the data as a string, which is text and as such you cant do math to it. So what you do it ask SQL to read the string and do math on it, which converts to an integer, then do the math you care about and re-save.

sarrigo

I can confirm that this worked for my purposes. I am very new to SQL so I am confused why using abs instead of sum works.?. I also really like how you were able to avoid issues of null values all in one query. That's way simpler than my idea of having a separate SW alert looking for null fields and setting them to 0!

adam.beedell

The abs here is being used as "give me a number" (rather than text, that looks like a number). The +1 bit is actually doing the math on it's own

In your original I think you're thinking of SUM like in excel, in SQL it's more like when in excel you select a whole column and see the little number in the bottom right