You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IoT SiteWise Grafana plugin throws an invalid request error when more than 16 asset properties are added to a dashboard. This happens across different queries. This is the same error returned from BatchGetAssetPropertyValueHistory and BatchGetAssetPropertyAggregates, which are limited to 16 entries per request. It appears the plugin is not creating batch requests correctly as the reason behind the bug. users are requesting to visualize up to 100 data streams.
Expected behavior:
There is no limit on the number of asset properties a dashboard can visualize.
Customers do not see an error when exceeding 16 asset properties.
The plugin should create a separate request for each batch of 16 raw historical asset property data streams, 16 aggregated historical asset property data streams, and 128 raw latest historical asset properties queries (i.e., requests are divided by their limits on request entries).
The plugin should combine queries across panels to minimize the number of requests being sent to the BatchGet* APIs. Note: this is likely occurring to some degree already and that's how we are getting this error, yet from @Tracy French's initial investigation, it was not obvious where this logic occurs.
Error message:
The text was updated successfully, but these errors were encountered:
The IoT SiteWise Grafana plugin throws an invalid request error when more than 16 asset properties are added to a dashboard. This happens across different queries. This is the same error returned from BatchGetAssetPropertyValueHistory and BatchGetAssetPropertyAggregates, which are limited to 16 entries per request. It appears the plugin is not creating batch requests correctly as the reason behind the bug. users are requesting to visualize up to 100 data streams.
Expected behavior:
Error message:
The text was updated successfully, but these errors were encountered: