41 minutes ago, mnagel said:
You are correct -- you cannot store text values in datapoint results, only numbers. The "cheat" workaround to this is to use auto-discovery in the datasource at a rapid enough rate that you can populate instance auto-properties with the test results that are (hopefully) close enough to true and then emit them to your integration. And you would need to implement the DS in Groovy (if not already) as auto instance properties are not supported in most other data collection types.
What you see in many datasources as a workaround to the numbers-only limitation is a hardcoded manual map of numbers to strings, typically only shown (truncated most of the time) in chart legends. I submitted a feature request long ago to make those first-class by creating enum mappings within datapoint definitions, allowing those strings to be used more generally. Sadly, as is the case for feature requests it is just a way to vent and not to actually get anything done. Most of the time, anyway.
I see, thanks for clarifying this. I might try this out if one other option I researched does not work.
Alternatively, I'm going to try and configure and EventSource with a custom Groovy script to execute the Stored Procedure and try to extract the results this way, so it accepts string output. Not sure if this will work either but I'm going to give it a shot. I appreciate the response @mnagel! Will keep that auto-discovery method as a backup.
