ExpertWQL Query Datapoint cant do Expressions or Scripts?
Because LogicMonitor can't do Text Datapoints (correct me if I'm wrong) and because a Config Source can't run as frequently as I would like, I'm trying to find a way to essentially turn an ENUM through some kind of hardcoding, into a numeric value. I need to turn a normal TEXT FIELD from a WQL Query into a number, something like State, aka ServiceControllerStatus:
1 Stopped
2 StartPending
3 StopPending
4 Running
5 ContinuePending
6 PausePending
7 Paused
But unfortunately I cant reference WQL query fields in the Complex datapoint section, but ONLY the complex datapoint section can do any kind of expressions. But it can only base those from the Normal datapoints, which all must be numeric.
So short of doing some complete hack where I have a "Normal" datapoint that converts a textmatch(BLAH) into a gauge via a regex for each of the above text strings (essentially having a bunch of normal datapoints by the above names returning 0 or 1) and THEN doing some horrendous if expression or something that embeds all the gauges in a 7-nested deep if statement that multiplies the 0 or 1 * its value I need displayed in a super ugly expression ..... OOF .....
I cant think of any other way to do that. But I have someone that needs to track these states aka ServiceControllerStatus values. None of the WQL Query fields that come back from "SELECT * from Win32_Service" have a numeric equivalent of the text value.
Just hoping there is some better way to do it. Thanks!
Would suggest switch it over to a full groovy/powershell script to collect the information. Then you can have real enums and convert the strings to numbers directly in the script. A lot of LM existing scripts this way. For example you can look at Microsoft_Windows_Services. You might be able to actually clone that one and re use it for your purposes.
Now that I HIGHLY suggest you order your status codes from good to bad. Because thresholds can't use and/or (like "=1 or =2"). So I would order your status to be something like:
0 StartPending
1 Running
2 ContinuePending
3 PausePending
4 Paused
5 StopPending
6 Stopped(I'm guessing the order). That way you can have a threshold of like "> 3 6". It also easier to read in a graph or color code in a table.
