Scriptmonitor - more than 10 script output-pairs

Extremely in favor of this. Why Solarwinds would think a reasonable application monitoring software would never have more than 10 ouputs is beyond me.

I also have the same issue : 10 output per script is really too low!

We have a lot of metrics to get via scripts on a some nodes...so we have to run dozens of scripts on the same node.

At some point it seems that SolarWinds can not handle that properly (too many scripts called I think?)

As a result we have some false-positive results from time to time (Unknow instead of OK).

To be able to get more than 10 output pairs would really help

In my case I am using this to collect DFS backlog using powershell monitor (because I have not found any better way to monitor DFS backlog).  This could return many pairs, lets say 30 pairs.  I am trying to get historic value or graphs of DFS backlog from server A to server B, A>C, B>C, and etc.  Again 20+ pairs. At present SW drops everything past 10 pairs and I can not find a way to collect this information programatically.  My workaround is to sort output by larger statistic and show me top 10.  Then use external SQL query to collect those into separate db and use homegrown SQL front end to generate graphs.  Not the best way, but it is what it is.  So, I am not I am following your solution there.

either the monitor could be configured with 'accept this many response pairs' or the script itself could dynamically supply that value.

For instance, a file system monitor for *nix that actually lists the user-observed values of mounte file systems (as to actual space free), could have as few as one response pair, but on some of our systems, as many as 30 or more response pairs.

Just accept an array in the response, then work through the array for the fields/values, and you should be ok. Shouldn't be that much for SW to figure out how to receive that kind of output and utilize it dynamically.

Thank you for clarification.

So, is there any idea if there are any plans on bringing these feature in some future release?

This tread is very open dated with no insight for the customer if this will ever be implemented.

Meanwhile, while supporting SW at my organization I am getting inquiries and do not have any answer to give.

I am sure you understand my frustration...