Sounds like youre using template variables. Check what is the datasource for the dashboard template variables. You need to define an explicit UID for your datasource. I did not want to post to correct server adress. Vast majority of metrics is not yet exposed on the graphs, but you can add them on your own Changelog added variable for DS_PROMETHEUS so that json file can be directly added to grafana data directory and solves errors such as Templating init failed Datasource named $ {DS_PROMETHEUS} was not found ` initial release Contact At the moment of writing this post the issue seems to be still open. Use that UID across all environments that your dashboards will be shared in. Note: By signing up, you agree to be emailed related product-level information. How to do a distinct count of a metric using graphite datasource in grafana? However when I manually go to the Grafana gui and do the import everything functions correctly. I think some of these issues might be resolved by #43263 but would like to confirm it. Well occasionally send you account related emails. Node exporterPromenadeAlertmanagerPrometheusbugbugbug
The error I'm getting in the logs is lvl=eror msg="Request Completed" method=POST path=/api/ds/query status=500. First, download the JSON file using the link provided on the dashboard page: Next, save the file in the grafana/provisioning/dashboards/ directory. Du you have a default datasource defined in Grafana ? EF & E-Series, SANtricity, and Related Plug-ins, Software Development Kit (SDK) and API Discussions, NetApp's Response to the Ukraine Situation. [root@kahn.xiao ~]# uname -a Did this satellite streak past the Hubble Space Telescope so close that it was out of focus? Add Data Source from grafana, got HTTP Error Bad Gateway error: Import dashboard 315 from: https://grafana.com/dashboards/315 Then check Kubernetes cluster monitoring (via Prometheus), got Templating init failed error: Why? For reference, we use loki and grafana as our datasources. Required fields are marked *, By using this form you agree with the storage and handling of your data by this website. grafanadashboarduserdatasourcedashboardgrafanagrafana-5.4.4 json model . *"},"inspect":{"type":"graphite"},"retry":0,"headers":{"Accept":"application/json, text/plain, */*"}},"statusText":"","xhrStatus":"error"},"cancelled":true}. Add data sourcePrometheus. Dashboard imported without filling template variables and when access those dashboards I see error. You made a cool dashboard, then clicked "Share" and exported to JSON. Styling contours by colour and by line thickness in QGIS. Grafana properly load this new dashboard, but such error occurs: 'Datasource named ${DS_GRAPHITE} was not found'. The URL needs to be accessible from the browser if you select this access mode. This will allow you to Export/Import dashboards between container tear downs, keeping your teammates happy. Provision dashboards and data sources | Grafana Labs "pluginName": "Graphite" {"err":{"data":null,"status":-1,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"http://:81/metrics/find","params":{"query":"netapp.perf7. Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2, How to show custom application metrics in Prometheus captured using the golang client library from all pods running in Kubernetes, How can I open the Jaeger UI(run in Istio) in a remote browser, not the localhost machine, Prometheus not scraping additional scrapes, Grafana dashboard not displaying pod name instead pod_name, deploy elk stack in kubernetes with helm VolumeBinding error, Unable To Access Prometheus Dashboard/ Port Forwarding Doesn't Work, Cant see Prometheus server on localhost:9090, Bulk update symbol size units from mm to map units in rule-based symbology, Follow Up: struct sockaddr storage initialization by network format-string. After that , we have created a new datasource Y (influxdb database Y) and change X by Y in all panels. When I'm trying to open any dashboard that I have I'm getting a following error message: Also in the browser console log I see the following messages: I'm getting the same error in browser console when I'm trying to Save & Test settings in Graphite datasource. Linear regulator thermal information missing in datasheet. If you're actually sharing your dashboards with random people on the internet. Is it possible to rotate a window 90 degrees if it has the same length and width? Grafana v8.4.6 (c53173f), grafana/public/app/features/plugins/datasource_srv.ts. "__inputs": [ Have you sorted this issue ? In effect, this file will configure a default data source for the default organisation in Grafana (identified with the id=1). We have made a dashboard, with graphs which was using a datasource named X (influxdb database X) . rev2023.3.3.43278. Well occasionally send you account related emails. Next, we need to mount this configuration to the grafana service. Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. @berghauz thanks. To avoid having your issue closed in the future, please read our CONTRIBUTING guidelines. So this dashboard is one that we did not do any manual intervention on and has two variables. Or you might have gone to Dashboard settings and selected "View as JSON" then copy-and-pasta'ed that json into a dashboard made through provisioning. Prometheus, https://blog.csdn.net/chenhongloves/article/details/125284763, prometheus operator servicemonitor label. Connect Grafana to data sources, apps, and more, with Grafana Alerting, Grafana Incident, and Grafana OnCall, Frontend application observability web SDK, Try out and share prebuilt visualizations, Contribute to technical documentation provided by Grafana Labs, Help build the future of open source observability software Is this on the roadmap, or do I just need to work around it? After that , we have created a new datasource Y (influxdb database Y) and change X by Y in all panels Thanks to the Grafana provisioning feature, we can use configuration files to set up everything before running the application for the first time. The dashboard appears in a Services folder. This seems like #11018, also. Grafana provisioning - How to configure data sources and dashboards Any leads on this would be highly appreciated! Already on GitHub? However, if we are loading it directly in a browser, we are able to see the snap shot getting rendered. I went back and manually imported 1471 and then did an import on it and did a diff to see what the difference was: Seems all the templating was done, and this section below was removed: The text was updated successfully, but these errors were encountered: Same issue here when trying to create a dashboard from a previously exported dashboard json, with grafana 4.5.2 and wizzy 0.6.0, pretty much making wizzy unusable for me at the moment :(. Trying to understand how to get this basic Fourier Series. The graph panels were updated to use the renamed datasource however dashboard variables were not updated and require manual intervention to fix. Created Grafana 7.5.3 container using the storage created: In Grafana created two data sources: Test DB (default) and a MySQL named MySQL-1. Connect and share knowledge within a single location that is structured and easy to search. Follow the issue template and add additional information that will help us replicate the problem. @nirorman Thank you about the answer, it works! Thanks for creating this issue! start grafana with default settings access grafana new url from new browser/new session, it forced me to change the default password open terminal and run the curl api command to create dummy datasource go back to browser session and verify new datasource created successfully Running Grafana 4.3.3 and I used wizzy to download dashboard 1471 version 1 Solution is given at #11018 by @torkelo (wish it had been properly documented at the original provisioning docu and in export/import) - Old datasource referenced: templating init failed datasource named XX not found Grafana templating gquentin December 20, 2017, 11:06am #1 We have made a dashboard, with graphs which was using a datasource named X (influxdb database X) . Hi, Fix Invalid CSRF token error add the XSRF-TOKEN header in Angular, To clarify optional configuration for Grafana provisioning, visit the. For this reason, edit the docker-compose.yml file to add the appropriate volume: We can use one of the predefined, ready to use Grafana dashboards to save time on configuration. Grafana HTTP Error Bad Gateway and Templating init failed errors By clicking Sign up for GitHub, you agree to our terms of service and We are able to generate the snapshot for a given panel using snapshotapi and while rendering the snapshot url in an iframe, we are getting "Template init failed Datasource named "x" was not found. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. How to set up Grafana with Docker and connect it to Prometheus, https://github.com/grafana/grafana/pull/11531, Support dashboard variables in dashboard provisioning. It will be great if I can change those inputs later or import as dashboard template and later import them with correct input in the app. Namely, under the /etc/grafana/provisioning/datasources directory. Workarounds that worked in Grafana 9.1.5: So you might be like me, you never defined a datasource UID in your provisioning file. Servershould be the preferred way if nothing else stated.Server access mode (Default):All requests will be made from the browser to Grafana backend/server which in turn will forward the requests to the data source and by that circumvent possible Cross-Origin Resource Sharing (CORS) requirements. Already on GitHub? Use the Kubernetes-internal IP or domain name. In short, add uid: to your datasource provisioning yaml: This will force Grafana to output all exported dashboards with the uid "myotheruidisanairplane". Henceforth, I simply replaced all the ${DS_PROMETHEUS} occurrences with the correct data source name Prometheus. Your review is pending approval, you can still make changes to it. Making statements based on opinion; back them up with references or personal experience. I'm also having issues with library panels during the provisioning process, and could do with help on that as well. Remember the version number for the version before the upgrade and then in the same browser where you're logged into Grafana try writing the following: /api/dashboards/id/74/versions/ Dashboard variables' datasource not updated when renaming data source, https://grafana.com/docs/grafana/latest/http_api/dashboard_versions/#get-dashboard-version, https://user-images.githubusercontent.com/562238/149457650-9d7f1558-50bc-4879-ad1b-670cdf2c1ca2.png, Grafana version: 8.3.3 (when rename occurred), Data source type & version: Influx v1.8.3, User OS & Browser: MacOS 11.5.1 w/ Chrome 96.0.4664.55, Query results from the inspect drawer (data tab & query inspector), Panel settings can be extracted in the panel inspect drawer JSON tab, Dashboard JSON can be found in the dashboard settings JSON model view. Therefore, we have to mount our folder to this location in the container: However, starting Grafana now will result in the Datasource named ${DS_PROMETHEUS} was not found error once we try to access the dashboard. I am facing similar issue? - the incident has nothing to do with me; can I use this this way? Grafana json dashboard Templating Failed to upgrade legacy Can I tell police to wait and call a lawyer when served with a search warrant? This is mainly a test of hdfs + nn + zk + jn in k8s: Upload an updated version of an exported dashboard.json file from Grafana. My end goal was to be able to start Grafana with both a Prometheus data source and a dashboard (the predefined JVM dashboard instance) already configured. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Upgrade to 8.3.3 (version we upgraded to), without opening the dashboard (this might be part of the issue based on the newly noticed message but it is also not a viable workaround if there are a large number of dashboards), rename the datasource. For more detail, feel free to browse the official datasource.yml file example. More info here: https://kubernetes.io/docs/concepts/services-networking/service/#headless-services, There's probably a better solution, but this is the only one I've found that actually works for me, with kube-prometheus. Doing some diffs locally to the previous version it looks like it was just dropping a panel. Is it possible to rotate a window 90 degrees if it has the same length and width? Below you can see the grafana directory containing files that I added to my project to supply Grafana configuration: According to my docker compose configuration the prometheus service is available for the other services running within the internal network under prometheus:9090 (http://localhost:9090/ in my browser). The issue is caused by the "datasource": "${DS_PROMETHEUS}" used in the jvm-micrometer_rev9.json file. message on all dashboards (ss below). "After the incident", I started to be more careful not to trip over things. Otus-DevOps-2017-11/Maksov_microservices#9, Otus-DevOps-2018-02/EugRomanchenko_microservices#10. Grafana is not able to get Prometheus metrics although Prometheus All in all, the issue occurs only when working with files downloaded from the Official and community dashboard page. You may need to adjust dashboard to match your prometheus labels, Vast majority of metrics is not yet exposed on the graphs, but you can add them on your own, added variable for DS_PROMETHEUS so that json file can be directly added to grafana data directory and solves errors such as. By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. Find centralized, trusted content and collaborate around the technologies you use most. Find the UID that Grafana assigned to the datasource in the JSON. When I try to upgrade to any 8.3.x I get an Internal Server Error - Check the Grafana server logs for the detailed error message. Old datasource referenced: templating init failed datasource named XX Open your dashboard json file. Thank you . It would be good to get a fix, or at least an official workaround. The dashboard JSON is as follows: docker stop grafana docker rm grafana docker run -d -p 3001:3000 --name=grafana -v grafana-storage:/var/lib/grafana grafana/grafana:8.4.6 We're trying to copy the json from our prod Grafana to our non-prod Grafana, and it shows the following errors. From: Why do many companies reject expired SSL certificates as bugs in bug bounties? It's an issue in 8.5.1 (Enterprise) as well. I managed to "fix" the problem manually, by editing the JSON file (the one created when exporting the dashboard), and changing every occurrence of ${DS_GRAPHITE} and DS_GRAPHITE (both variations appear) to the explicit name I gave to my Data-source (in my case, just Graphite). Follow the workaround, and find-and-replace all UIDs to be a null-string. The $ {DS_GRAPHITE} is a variable name from my Grafana configuration and is not recognized by your Grafana server. Mississippi High School Basketball Player Rankings 2023,
Who Owns Worthington Foods,
Articles G
">
grafana templating init failed datasource named was not found
grafana templating init failed datasource named was not found
Because of it, remember to specify the orgId option accordingly for your data sources if needed. Replacing all instances of ${DS_PROMETHEUS} in the dashboard's json with just Prometheus directly worked around the issue. Seems like the "__inputs": [] are removed and I also get the issue of: Same here with an InfluxDB datasource : all JSON exported datasources are prefixed with DS, making export/import from one environment to the other fail, Same here with Grafana 4.4.3 and Graphite data source: The dashboard JSON is as follows: The template variable seems to be updated correctly, as in the following dashboard JSON. { Should be straight-forward, right?, but then you bring your Dashboard.json to a new Grafana instance only to find the data didn't load. Sounds like youre using template variables. Check what is the datasource for the dashboard template variables. You need to define an explicit UID for your datasource. I did not want to post to correct server adress. Vast majority of metrics is not yet exposed on the graphs, but you can add them on your own Changelog added variable for DS_PROMETHEUS so that json file can be directly added to grafana data directory and solves errors such as Templating init failed Datasource named $ {DS_PROMETHEUS} was not found ` initial release Contact At the moment of writing this post the issue seems to be still open. Use that UID across all environments that your dashboards will be shared in. Note: By signing up, you agree to be emailed related product-level information. How to do a distinct count of a metric using graphite datasource in grafana? However when I manually go to the Grafana gui and do the import everything functions correctly. I think some of these issues might be resolved by #43263 but would like to confirm it. Well occasionally send you account related emails. Node exporterPromenadeAlertmanagerPrometheusbugbugbug
The error I'm getting in the logs is lvl=eror msg="Request Completed" method=POST path=/api/ds/query status=500. First, download the JSON file using the link provided on the dashboard page: Next, save the file in the grafana/provisioning/dashboards/ directory. Du you have a default datasource defined in Grafana ? EF & E-Series, SANtricity, and Related Plug-ins, Software Development Kit (SDK) and API Discussions, NetApp's Response to the Ukraine Situation. [root@kahn.xiao ~]# uname -a Did this satellite streak past the Hubble Space Telescope so close that it was out of focus? Add Data Source from grafana, got HTTP Error Bad Gateway error: Import dashboard 315 from: https://grafana.com/dashboards/315 Then check Kubernetes cluster monitoring (via Prometheus), got Templating init failed error: Why? For reference, we use loki and grafana as our datasources. Required fields are marked *, By using this form you agree with the storage and handling of your data by this website. grafanadashboarduserdatasourcedashboardgrafanagrafana-5.4.4 json model . *"},"inspect":{"type":"graphite"},"retry":0,"headers":{"Accept":"application/json, text/plain, */*"}},"statusText":"","xhrStatus":"error"},"cancelled":true}. Add data sourcePrometheus. Dashboard imported without filling template variables and when access those dashboards I see error. You made a cool dashboard, then clicked "Share" and exported to JSON. Styling contours by colour and by line thickness in QGIS. Grafana properly load this new dashboard, but such error occurs: 'Datasource named ${DS_GRAPHITE} was not found'. The URL needs to be accessible from the browser if you select this access mode. This will allow you to Export/Import dashboards between container tear downs, keeping your teammates happy. Provision dashboards and data sources | Grafana Labs "pluginName": "Graphite" {"err":{"data":null,"status":-1,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"http://:81/metrics/find","params":{"query":"netapp.perf7. Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2, How to show custom application metrics in Prometheus captured using the golang client library from all pods running in Kubernetes, How can I open the Jaeger UI(run in Istio) in a remote browser, not the localhost machine, Prometheus not scraping additional scrapes, Grafana dashboard not displaying pod name instead pod_name, deploy elk stack in kubernetes with helm VolumeBinding error, Unable To Access Prometheus Dashboard/ Port Forwarding Doesn't Work, Cant see Prometheus server on localhost:9090, Bulk update symbol size units from mm to map units in rule-based symbology, Follow Up: struct sockaddr storage initialization by network format-string. After that , we have created a new datasource Y (influxdb database Y) and change X by Y in all panels. When I'm trying to open any dashboard that I have I'm getting a following error message: Also in the browser console log I see the following messages: I'm getting the same error in browser console when I'm trying to Save & Test settings in Graphite datasource. Linear regulator thermal information missing in datasheet. If you're actually sharing your dashboards with random people on the internet. Is it possible to rotate a window 90 degrees if it has the same length and width? Grafana v8.4.6 (c53173f), grafana/public/app/features/plugins/datasource_srv.ts. "__inputs": [ Have you sorted this issue ? In effect, this file will configure a default data source for the default organisation in Grafana (identified with the id=1). We have made a dashboard, with graphs which was using a datasource named X (influxdb database X) . rev2023.3.3.43278. Well occasionally send you account related emails. Next, we need to mount this configuration to the grafana service. Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. @berghauz thanks. To avoid having your issue closed in the future, please read our CONTRIBUTING guidelines. So this dashboard is one that we did not do any manual intervention on and has two variables. Or you might have gone to Dashboard settings and selected "View as JSON" then copy-and-pasta'ed that json into a dashboard made through provisioning. Prometheus, https://blog.csdn.net/chenhongloves/article/details/125284763, prometheus operator servicemonitor label. Connect Grafana to data sources, apps, and more, with Grafana Alerting, Grafana Incident, and Grafana OnCall, Frontend application observability web SDK, Try out and share prebuilt visualizations, Contribute to technical documentation provided by Grafana Labs, Help build the future of open source observability software Is this on the roadmap, or do I just need to work around it? After that , we have created a new datasource Y (influxdb database Y) and change X by Y in all panels Thanks to the Grafana provisioning feature, we can use configuration files to set up everything before running the application for the first time. The dashboard appears in a Services folder. This seems like #11018, also. Grafana provisioning - How to configure data sources and dashboards Any leads on this would be highly appreciated! Already on GitHub? However, if we are loading it directly in a browser, we are able to see the snap shot getting rendered. I went back and manually imported 1471 and then did an import on it and did a diff to see what the difference was: Seems all the templating was done, and this section below was removed: The text was updated successfully, but these errors were encountered: Same issue here when trying to create a dashboard from a previously exported dashboard json, with grafana 4.5.2 and wizzy 0.6.0, pretty much making wizzy unusable for me at the moment :(. Trying to understand how to get this basic Fourier Series. The graph panels were updated to use the renamed datasource however dashboard variables were not updated and require manual intervention to fix. Created Grafana 7.5.3 container using the storage created: In Grafana created two data sources: Test DB (default) and a MySQL named MySQL-1. Connect and share knowledge within a single location that is structured and easy to search. Follow the issue template and add additional information that will help us replicate the problem. @nirorman Thank you about the answer, it works! Thanks for creating this issue! start grafana with default settings access grafana new url from new browser/new session, it forced me to change the default password open terminal and run the curl api command to create dummy datasource go back to browser session and verify new datasource created successfully Running Grafana 4.3.3 and I used wizzy to download dashboard 1471 version 1 Solution is given at #11018 by @torkelo (wish it had been properly documented at the original provisioning docu and in export/import) - Old datasource referenced: templating init failed datasource named XX not found Grafana templating gquentin December 20, 2017, 11:06am #1 We have made a dashboard, with graphs which was using a datasource named X (influxdb database X) . Hi, Fix Invalid CSRF token error add the XSRF-TOKEN header in Angular, To clarify optional configuration for Grafana provisioning, visit the. For this reason, edit the docker-compose.yml file to add the appropriate volume: We can use one of the predefined, ready to use Grafana dashboards to save time on configuration. Grafana HTTP Error Bad Gateway and Templating init failed errors By clicking Sign up for GitHub, you agree to our terms of service and We are able to generate the snapshot for a given panel using snapshotapi and while rendering the snapshot url in an iframe, we are getting "Template init failed Datasource named "x" was not found. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. How to set up Grafana with Docker and connect it to Prometheus, https://github.com/grafana/grafana/pull/11531, Support dashboard variables in dashboard provisioning. It will be great if I can change those inputs later or import as dashboard template and later import them with correct input in the app. Namely, under the /etc/grafana/provisioning/datasources directory. Workarounds that worked in Grafana 9.1.5: So you might be like me, you never defined a datasource UID in your provisioning file. Servershould be the preferred way if nothing else stated.Server access mode (Default):All requests will be made from the browser to Grafana backend/server which in turn will forward the requests to the data source and by that circumvent possible Cross-Origin Resource Sharing (CORS) requirements. Already on GitHub? Use the Kubernetes-internal IP or domain name. In short, add uid: to your datasource provisioning yaml: This will force Grafana to output all exported dashboards with the uid "myotheruidisanairplane". Henceforth, I simply replaced all the ${DS_PROMETHEUS} occurrences with the correct data source name Prometheus. Your review is pending approval, you can still make changes to it. Making statements based on opinion; back them up with references or personal experience. I'm also having issues with library panels during the provisioning process, and could do with help on that as well. Remember the version number for the version before the upgrade and then in the same browser where you're logged into Grafana try writing the following: /api/dashboards/id/74/versions/ Dashboard variables' datasource not updated when renaming data source, https://grafana.com/docs/grafana/latest/http_api/dashboard_versions/#get-dashboard-version, https://user-images.githubusercontent.com/562238/149457650-9d7f1558-50bc-4879-ad1b-670cdf2c1ca2.png, Grafana version: 8.3.3 (when rename occurred), Data source type & version: Influx v1.8.3, User OS & Browser: MacOS 11.5.1 w/ Chrome 96.0.4664.55, Query results from the inspect drawer (data tab & query inspector), Panel settings can be extracted in the panel inspect drawer JSON tab, Dashboard JSON can be found in the dashboard settings JSON model view. Therefore, we have to mount our folder to this location in the container: However, starting Grafana now will result in the Datasource named ${DS_PROMETHEUS} was not found error once we try to access the dashboard. I am facing similar issue? - the incident has nothing to do with me; can I use this this way? Grafana json dashboard Templating Failed to upgrade legacy Can I tell police to wait and call a lawyer when served with a search warrant? This is mainly a test of hdfs + nn + zk + jn in k8s: Upload an updated version of an exported dashboard.json file from Grafana. My end goal was to be able to start Grafana with both a Prometheus data source and a dashboard (the predefined JVM dashboard instance) already configured. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Upgrade to 8.3.3 (version we upgraded to), without opening the dashboard (this might be part of the issue based on the newly noticed message but it is also not a viable workaround if there are a large number of dashboards), rename the datasource. For more detail, feel free to browse the official datasource.yml file example. More info here: https://kubernetes.io/docs/concepts/services-networking/service/#headless-services, There's probably a better solution, but this is the only one I've found that actually works for me, with kube-prometheus. Doing some diffs locally to the previous version it looks like it was just dropping a panel. Is it possible to rotate a window 90 degrees if it has the same length and width? Below you can see the grafana directory containing files that I added to my project to supply Grafana configuration: According to my docker compose configuration the prometheus service is available for the other services running within the internal network under prometheus:9090 (http://localhost:9090/ in my browser). The issue is caused by the "datasource": "${DS_PROMETHEUS}" used in the jvm-micrometer_rev9.json file. message on all dashboards (ss below). "After the incident", I started to be more careful not to trip over things. Otus-DevOps-2017-11/Maksov_microservices#9, Otus-DevOps-2018-02/EugRomanchenko_microservices#10. Grafana is not able to get Prometheus metrics although Prometheus All in all, the issue occurs only when working with files downloaded from the Official and community dashboard page. You may need to adjust dashboard to match your prometheus labels, Vast majority of metrics is not yet exposed on the graphs, but you can add them on your own, added variable for DS_PROMETHEUS so that json file can be directly added to grafana data directory and solves errors such as. By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. Find centralized, trusted content and collaborate around the technologies you use most. Find the UID that Grafana assigned to the datasource in the JSON. When I try to upgrade to any 8.3.x I get an Internal Server Error - Check the Grafana server logs for the detailed error message. Old datasource referenced: templating init failed datasource named XX Open your dashboard json file. Thank you . It would be good to get a fix, or at least an official workaround. The dashboard JSON is as follows: docker stop grafana docker rm grafana docker run -d -p 3001:3000 --name=grafana -v grafana-storage:/var/lib/grafana grafana/grafana:8.4.6 We're trying to copy the json from our prod Grafana to our non-prod Grafana, and it shows the following errors. From: Why do many companies reject expired SSL certificates as bugs in bug bounties? It's an issue in 8.5.1 (Enterprise) as well. I managed to "fix" the problem manually, by editing the JSON file (the one created when exporting the dashboard), and changing every occurrence of ${DS_GRAPHITE} and DS_GRAPHITE (both variations appear) to the explicit name I gave to my Data-source (in my case, just Graphite). Follow the workaround, and find-and-replace all UIDs to be a null-string. The $ {DS_GRAPHITE} is a variable name from my Grafana configuration and is not recognized by your Grafana server.
You must be fatal car accident in kentucky august 2020 to post a comment.