Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashboard limited to 16 total asset properties #348

Closed
hwandersman opened this issue Aug 16, 2024 · 0 comments · Fixed by #355
Closed

Dashboard limited to 16 total asset properties #348

hwandersman opened this issue Aug 16, 2024 · 0 comments · Fixed by #355

Comments

@hwandersman
Copy link
Collaborator

hwandersman commented Aug 16, 2024

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:

image

@hwandersman hwandersman added type/bug Something isn't working datasource/Sitewise labels Aug 16, 2024
@iwysiu iwysiu moved this from Incoming to Next in AWS Datasources Aug 19, 2024
@kevinwcyu kevinwcyu self-assigned this Sep 4, 2024
@kevinwcyu kevinwcyu moved this from Next to In Progress in AWS Datasources Sep 4, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in AWS Datasources Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants