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

Getting duplicate legends in Grafana when using selecting for a particular measure_name #161

Closed
flycast opened this issue Apr 18, 2022 · 1 comment

Comments

@flycast
Copy link

flycast commented Apr 18, 2022

What happened:
I have data with multiple measurements in AWS Timestream. When I use the following query I get multiple data legends:
SELECT * FROM "sampleDB"."LgFlaminator" where measure_name = 'PolyPressure'

image

What you expected to happen:
I expected that I would get a single data series with a single legend.
I find that I have to call the query like this to get the result I wanted:
SELECT time, measure_value::double FROM "sampleDB"."LgFlaminator" where measure_name = 'PolyPressure'

image

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

Example:

  1. Add multiple data points for two different measurement names to Timestream.
  2. Create query

Anything else we need to know?:

Environment:

  • Grafana version: Cloud v8.4.6 (c53173ff6)
  • Plugin version: AWS Timestream plugin 1.5.1
  • OS Grafana is installed on: Cloud version
  • User OS & Browser: Windows 10, Chrome
@sarahzinger
Copy link
Member

@flycast I see 2 markers like that when the table I'm trying to query has 2 numeric columns, perhaps if you switch to a table view, you'll see something similar that could explain what is going on:

Screen Shot 2022-04-18 at 1 58 56 PM

In the case above, AWS is returning back to us 2 columns that I believe can be the same value in different formats for the same measurement (although interestingly in this sample dataset, one of the columns is always empty)

The visualization does not know which column you would like to render and so it renders both. As you point out you can use sql syntax to narrow down to render just the fields you are interested in.

I believe this is as designed so I'll close the issue, but if I'm misunderstanding something let me know and I'm happy to reopen it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants