This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

API Poller Large Numeric Values and Modern Dashboard 32-bit SWQL Limitations

The value returned for storage usage by the Microsoft 365 Exchange Mailbox template is specified in bytes.  However, when you have a medium sized tenant or larger where your storage usage is as large as hundreds of gigabytes or terabytes, you hit a limitation in SWQL where you can't use this value in a modern dashboard widget because the number it too large to fit into a 32-bit integer.  The value itself is too large to use as a metric, and you can't perform any arithmetic against it to convert it to a different unit with a smaller value (such as GB or TB) due to a 32-bit integer overflow.

Is there a workaround to deal with these large values?  Is there some way to force SWQL to use 64-bit vs 32-bit integers?

  •   Thanks for describing the use case. There is no workaround to support such large values, it would be good to have "transform" option, so that value is converted to e.g. GB. Could you create feature request for that, so others could vote for it?

    As for the question: "Is there some way to force SWQL to use 64-bit vs 32-bit integers?" - there is no such option at the moment.

  • Workaround i've got in use is you save the large numeric value in one API poller, then use another to query solarwinds through SWQL, then stick the secondary api poller on dashboards.

    Example:

    https://127.0.0.1:17778/SolarWinds/InformationService/v3/Json/Query?query=Select+ROUND%28%28MIN%28Total%29%2FMAX%28Total%29%2A100%29%2C2%29+as+PercentageUsed+FROM+%28%0D%0ASELECT+SUM%28ABS%28METRIC%29%29%2F1024%0D%0AAS+Total+FROM+Orion.APIPoller.ValueToMonitor+vtm+where+ID+in+%28187%2C188%29+Group+by+ID%0D%0A%29+AS+SumCalc

    Note it's not very readable, but if you take a working SWQL query from SWQL studio and run it through https://www.url-encode-decode.com/ you get something useable

    Also Note the division is fiddily for those same reasons you specified.

    Also also note you can do percentages this way. - an easier method would me awesome mind