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

Get interpolated property values quality "ANY" #326

Closed
hwandersman opened this issue Jun 13, 2024 · 2 comments · Fixed by #342
Closed

Get interpolated property values quality "ANY" #326

hwandersman opened this issue Jun 13, 2024 · 2 comments · Fixed by #342
Assignees

Comments

@hwandersman
Copy link
Collaborator

hwandersman commented Jun 13, 2024

What happened:
Updated the "Quality" setting of Get interpolated property values to "GOOD" then "ANY" and saw an error:
image

The value "ANY" is used as a quality setting instead of the accepted values "GOOD", "BAD", or "UNCERTAIN". Bug with how this value is handled in the query editor and backend datasource mapping.

What you expected to happen:
Data is successfully fetched for any quality.

How to reproduce it (as minimally and precisely as possible):

  1. Add a query for "Get interpolated property values"
  2. Choose an asset and asset property (DOUBLE value type)
  3. Change the "Quality" setting to "GOOD"
  4. Change the "Quality" setting to "ANY"
  5. See the error

Screenshots

Screen.Recording.2024-06-13.at.2.31.15.PM.mov

Anything else we need to know?:

Environment:

  • Grafana version: 9.4.0
  • Plugin version: 1.12.1
  • OS Grafana is installed on: MacOS
  • User OS & Browser: Sonoma 14.5, Chrome
  • Others: Amazon Managed Grafana environment
@hwandersman
Copy link
Collaborator Author

Tested again on the plugin version 1.20.0 and saw the same issue.

@sarahzinger sarahzinger moved this from Incoming to Next in AWS Datasources Jun 14, 2024
@sarahzinger
Copy link
Member

I was able to recreate this on 1.21 as well. The first time with Any selected succeeded, then the second time failed. Going to share this with the team to see if we can prioritize it, I imagine an easy fix.

@iwysiu iwysiu self-assigned this Jul 12, 2024
@iwysiu iwysiu moved this from Next to In Progress in AWS Datasources Jul 12, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in AWS Datasources Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants