The API poller that has been introduced has been very powerful. However, it is mandatory (per coding) that it handles any output and converts it to an integer. I'm not sure who came up with that idea, but no! That's not enough.
I want the API poller to be able to accept strings and have them be a part of the MESSAGE that goes alongside with a status, so that we can actually capture useful information outside of just a status. Example: this poolAlias is important.
vs what I'd like to see: :
IE: if the message has an error message, right now all I can get is an integer out of that error message. I want that message to be able to be tied, at least the way SAM handles a statistic variable and a message variable. Otherwise I have no reason to use the API poller and not use something else, because I can't capture errors.
I'd consider this basic functionality as an expectation.
