We have stumbled across a problem with the Web Alert Manager getting alert rules with primary and secondary complex trigger stages to execute properly.
Here is an example of what I'm talking about, we have an instance of a primary custom SQL trigger that is working correctly and returns 87 rows:
But what we would really like to be able to do is (below) use both SQL and non-SQL together to produce the same
results as the SQL only trigger from above:
The above multistage trigger does not work correctly even though it's basically the same thing except I'm using
the GUI based drop downs in the secondary stage. When this trigger fires it produces several thousand rows
instead of the 87 from the original custom SQL primary only trigger. We don't want to have to deconstruct all of
the alert rule triggers in SolarWinds down to a custom SQL only primary trigger, that would be a nightmare.
I'm I missing something here in the difference between the above two scenarios?