-
Notifications
You must be signed in to change notification settings - Fork 19
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
Unable to view DB tables even though connection successful (AWS Timestream) #30
Comments
Same for me, Grafana v7.3.6 (ea06633c34) and Amazon Timestream plugin 1.1.1. The plugin seems to be working OK, existing panels still have data and I can run things like "SHOW TABLES FROM $__database" in Explore as long as I manually enter the DB name against the Macro field. It was working on 7.3.4. |
This been resolved in v1.1.1 |
Confirmed, everything working again with v1.1.2 |
Correction, the fixed version now places double quotes around $__measure preventing it from being used in queries. Existing queries seem to be working, but new ones cannot be created. e.g. This does not work Neither does using measure_name = $__measure, but using measure_name = 'com_select' does work. |
looks like this is resolved |
I'm having an issue with this. No matter which authorizer I use, when attempting to find Databases for Timestream I'm getting "Bad Gateway error." Looking at dev tools console it shows various 502 and 404 errors around not finding it. I made sure my Grafana is set up in public subnets to all traffic in and out, I even add AdministratorAccess to the Service Managed role created by grafana with no luck. It just errors out when attempting to see Databases. |
@RaistlinD2x-Dev did you manage to resolve the issue in the end? I am having the same issue. |
I am trying to use Grafana to connect and visualize data from AWS Timestream. I am able to connect to Timestream and view all the databases associated with the access/secret key I have provided; however, I cannot see any of the tables within any DB.
The text was updated successfully, but these errors were encountered: