-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fetch error: 404 Not Found Instantiating; when trying to add Athena data source #31
Comments
Did you look at the response in #28 ? |
Yes I did. I did clone the latest master so I have PluginAdminEnabled set to true in the yml file. I did follow the instructions from 1-5 to install Athena and the installation succeeds. The issue is with adding a Data Source. |
I was able to reproduce the problem and it is related to manager grafana. I asked internally if there is any solutions. |
So apparently, this is because the plugin is not fully installed. It's suggested to wait up to 5 minutes to have the plugin fully installed and try to add a data source. |
Thanks for the suggestion to wait 5 minutes. That worked and I was able to add an Athena data source. After doing so and executing the
Is there a null value of some sorts in one of the Athena Workgroup fields? We were not using Athena before this, so there might be some basic setting that I haven't turned on or such. |
Did you run any jobs through AWS Batch? A job must go through AWS Batch and complete with Success or Failure to generate the field for Athena. |
Yes I have container insights enabled for one ECS cluster, which corresponds to a queue on Batch. We have jobs regularly running on that queue. So could there be anything else causing the error? |
Did you have a job completed? I am unable to reproduce the error you are observing. |
When I inspect the query executed in the grafana dashboard on the athena datasource I see this query However when I look at my table in Athena, it just has these three columns, |
Can you check dynamodb to check if there is a started at field? |
These are the columns in dynamodb I initially didn't have container insights turned on for any of my ECS clusters. I did so for one cluster and then ran the dashboard creation python script. I printed out the clusterArn here https://github.com/aws-samples/aws-batch-operational-dashboards/blob/main/generate-grafana-dashboard.py#L71 and the cluster which had container insights enabled got printed out. |
The lack of a trail in cloudtrail is probably the cause. I'll try to find an account without trail to confirm in a couple of days. |
@uray-scalebio did the creation of a trail solve your challenges? |
@uray-scalebio looking back at your message regarding your DynamoDB content. "containerProperties": {
"vcpus": 2
"memory": 2048
} Both of those are deprecated per documentation. "containerProperties": {
"resourceRequirements": [
{
"type": "MEMORY",
"value": "2048"
},
{
"type": "VCPU",
"value": "2"
}
]
} |
Any update? |
Hello,
When I try to add an Amazon Athena Data Source, I get this error below
I do not get prompted to add any information related to the Athena data source, as is shown in your tutorial. The moment I click on athena in the add data source page, it shows me "Data Source added" and I immediately get the error in the screenshot above.
I've tried the Athena plugin version 2.13.5 and 2.14.0. I am running Grafana 9.4.
Is Athena part of the Enterprise Plugins and is that why I'm getting this error?
The text was updated successfully, but these errors were encountered: