Datasource not found error for some users on loading dashboards

[shahdevangp]

Hello,

Some users are facing the error "Templating: Failed to upgrade legacy queries Datasource i690Gzynk was not found". See the screenshots. I have built these dashboards and I am able to see the dashboards correctly. I don't get any error. Other users are getting this error. I have double-checked the data source settings, and everything looks ok.

[andresmgot]

Hi @shahdevangp,

The problem is that the UID of the data source in your Grafana instance is not the same than the one in which the dashboard is imported. To share a dashboard, you need to create a dashboard variable for the data source. Go to settings > variables and add a new variable for the data source:

Then you can reference that variable in your panels:

That way, the data source will be dynamically resolved in the importer env.

[shahdevangp]

We have not imported any dashboards. We have been working in the same instance. Also, if there is a mismatch in the UID, then it should be for everyone and not just for a few users. When I load the dashboard, I don't get any errors. Other users are getting this error.

[andresmgot]

Got it, if it's the same instance then it could be that those users don't have permissions to access the data source?

If that is not the case, to try to reproduce the issue, how have you defined the variables?

[shahdevangp]

Check the screenshots below on how the variables have been defined.

[shahdevangp]

They were able to see the dashboard yesterday. They cant see it today. I can put my finger on what changed between yday and today.

[andresmgot]

The variable definition seems fine.

then it could be that those users don't have permissions to access the data source?

Can you check if this can be the case? Something should have changed in the administration side that caused this, does not seem a plugin issue.

[shahdevangp]

It was a permission issue. Users were granted the right permissions and this error went away. I think the error message could be more helpful as it did not point to a permission issue.

[yaelleC]

Thanks for letting us know @shahdevangp
I have raised an issue to improve our error messaging

Closing this as resolved