AverageMemoryWorkingSet memory can only be monitored in an API poller via bytes instead of gigabytes due to Microsoft allowing a more granular look of memory usage. SolarWinds cannot be used to monitor AverageMemoryWorkingSet of API pollers due to the following error being received, when one tries to configure gigabyte monitoring: This value is too big. It would be great if SolarWinds could be configured to allow API pollers to monitor gigabytes to allow monitoring to occur in one location. Thank you.
