grafana templating init failed datasource named was not found

Grafana v7.5.3 (3e3cf4d) What is the purpose of non-series Shimano components? 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 :(. "description": "", If you don't specify an id in the dashboard definition, then Grafana assigns one during . kubernetes monitoring grafana prometheus minikube Share Follow asked Jan 19, 2018 at 9:44 online 4,489 10 32 47 Add a comment However when I manually go to the Grafana gui and do the import everything functions correctly. Open your dashboard json file. wizzy export dashboards "name": "DS_GRAPHITE", For me, there wasn't even an error or log which was frustrating. Docker & Chrome, What did you do? Making statements based on opinion; back them up with references or personal experience. SCRIPT - Absolute path to shell script to execute after a configmap got reloaded. Check what is the datasource for the dashboard template variables. Installed graphite, grafana and harvest 1.4.2 based on NetApp_Harvest_IAG_1.4.2.pdf and Graphite_Grafana_Quick_Start_v1.4.pdf (Ubuntu 14 based) . Just ran into this myself. For reference, we use loki and grafana as our datasources. I mean we should be able to copy output json with dashboard data and paste it while importing, receiving exactly the same dashboard without some annoying warnings. How do I align things in the following tabular environment? In exported .json file I have properly defined DS_GRAPHITE variable and I wonder why I have such output? 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. Linux client 3.10.0-957 Have you sorted this issue ? By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. ], It seems very similar to this issue in Grafana 4.0: #6189. I was never able to find a "proper" fix, but I found a workaround: By setting the clusterIP to None, the service changes to "Headless" mode, which means that requests are sent directly to a random one of the pods in that service/cluster. Therefore, you cant specify the http://localhost:9090 or http://127.0.0.1:9090 as the datasource urls. privacy statement. It's a firewall issue. Thank you . 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. Downloads. To avoid having your issue closed in the future, please read our CONTRIBUTING guidelines. This will either look like a random string (e.g. I've tried to reproduce the issue with the following steps. Consequently, we need to create the dashboard.yml file in the same folder to make Grafana use our JVM dashboard config: Below youll find a short description of used options: In the dashboard.yml file we specified the /etc/grafana/provisioning/dashboards as the path used by our Default provider. prometheus:9090. In another dashboard where I have different data source (namely Azure Monitor) I got the same type and uid. You made a cool dashboard, then clicked "Share" and exported to JSON. How to deal with the Datasource named ${DS_PROMETHEUS} was not found error:For me, what worked best was to use Import button on the Dashboards Manage screen.If I use that, it asks for the real datasource and replaces in during the import automatically (! In this article, Im going to work with the spring-boot-log4j-2-scaffolding project where I already use Prometheus to collect monitoring data on a Spring Boot application. Well demo all the highlights of the major release: new and updated visualizations and themes, data source improvements, and Enterprise features. This will allow you to Export/Import dashboards between container tear downs, keeping your teammates happy. How do you ensure that a red herring doesn't violate Chekhov's gun? In order to use it as a data source for Grafana, specify the minimal required configuration in the provisioning/datasources/datasource.yml file: Remember that we can use environment variables instead of hardcoded values. When they're exported using the API, the datasource name is hardcoded to whatever it was set in this particular instance; when exported using the UI the DS_* templating is added. I did not want to post to correct server adress. Powered by Discourse, best viewed with JavaScript enabled. How to reproduce it (as minimally and precisely as possible): Unclear. 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. What video game is Charlie playing in Poker Face S01E07? 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). If you run an older version of Grafana and want to share a dashboard on Grafana.com you need to manually add the inputs and templatize the datasource properties like above. We have made a dashboard, with graphs which was using a datasource named X (influxdb database X) . The nature of simulating nature: A Q&A with IBM Quantum researcher Dr. Jamie We've added a "Necessary cookies only" option to the cookie consent popup. It is now read-only. where key is '' and thus the error appears as Datasource was not found (whitespace is collapsed by the web browser). Linear regulator thermal information missing in datasheet. Workarounds that worked in Grafana 9.1.5: So you might be like me, you never defined a datasource UID in your provisioning file. Thanks to that, you can easily test the setup on your local machine. grafanadashboarduserdatasourcedashboardgrafanagrafana-5.4.4 json model . Can I tell police to wait and call a lawyer when served with a search warrant? 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 If you're actually sharing your dashboards with random people on the internet. Therefore, some data may be missing from the view over time: In addition to creating a custom dashboard, you can try to find a newer community dashboard: As a result, you will have a more up-to-date dashboard configuration that wont skip data: Thanks for this document, help me a lot to understood how deploy datasources and dashboards in my case from puppet! , pannelexport, Already on GitHub? You need to define an explicit UID for your datasource. Hi @bmagistro could you add a dashboard JSON example or more detalied repro steps. *"},"inspect":{"type":"graphite"},"retry":0,"headers":{"Accept":"application/json, text/plain, */*"}},"statusText":"","xhrStatus":"error"},"cancelled":true}. document.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() ); $ docker-compose up -d app prometheus grafana, lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning", lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning, # grafana/provisioning/datasources/datasource.yml, # grafana/provisioning/dashboards/dashboard.yml, Grafana provisioning How to configure data sources and dashboards. For data visualization issues: For authentication, provisioning and alerting issues, Grafana server logs are useful. ), Minimising the environmental effects of my dyson brain, Full text of the 'Sri Mahalakshmi Dhyanam & Stotram'. It's an issue in 8.5.1 (Enterprise) as well. Just ran into this issue on Grafana v5.0.4 (commit: 7dc36ae) when importing dashboards exported from another environment. 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. Can I save somewhere dashboards for now, so that they showed up in dashboards tab in data sources like official? Additionaly, you can find other solutions in this StackOverflow question. I think some of these issues might be resolved by #43263 but would like to confirm it. 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) . Ideally, when renaming a datasource, the variables associated with the dashboard would also be updated. I did not notice this before, but also seeing a "Templating; Failed to upgrade legacy queries Datasource was not found" message when loading this one. Created a query variable using MySQL-1 data source. All graphs works but each time we choose this dashboard, we have an error popup templating init failed, datasource named X was not found. We think it's missing some basic information. 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. Then I exported it to .json file and added, with changed name, to 'provisioning/dashboards' directory. Is there a single-word adjective for "having exceptionally strong moral principles"? To: 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. What sort of strategies would a medieval military use against a fantasy giant? Required fields are marked *, By using this form you agree with the storage and handling of your data by this website. Make sure that youve selected the correct datasource there as well. { "error": { "message": "Datasource named ${DS_LOCAL_GRAPHITE} was not found" } }. Not the answer you're looking for? Remember that: The URL needs to be accessible from the grafana backend/server if you select this [proxy] access mode. We upgraded from 7.2.1 -> 8.3.3, as part of the cleanup we renamed a couple datasources. I installed Grafana and Prometheus using helm charts. ServiceMonitor to scrape metrics - you must add ti on your own. @vlatk0o that's the one I was using too. "label": "graphite", Otus-DevOps-2017-11/Maksov_microservices#9, Otus-DevOps-2018-02/EugRomanchenko_microservices#10. Support dashboard variables in dashboard provisioning, https://github.com/grafana/grafana/blob/master/public/app/plugins/datasource/graphite/plugin.json#L7, Grafana 5 datasource for variables/templating/panels are not assigned, [Feature request] Add dashboard import by environment variable, Failing automatic provisioning of Grafana Dashboards previously exported or coming from grafana.com, fix: datasource not found in dashboard provisioning, nixos/grafana: Allow setting UID for datasource, No automatic import of Grafana dashboards, Incorrect variable when importing Dashboard, https://grafana.com/docs/grafana/latest/administration/provisioning/#example-data-source-config-file, Grafana dashboard maintenance/authoring (epic), Add hard coded job name to work with dashboard provisioning, Add dashboard variables to customize beacon/validator job name, Add dashboard variables to customize beacon/validator job name (, Failed to upgrade legacy queries Datasource ${DS_PROMETHEUS} was not found. Is a PhD visitor considered as a visiting scholar? Find centralized, trusted content and collaborate around the technologies you use most. It would be good to get a fix, or at least an official workaround. Use the view json feature from dashboard settings view to get the dashboard json". Namely, under the /etc/grafana/provisioning/datasources directory. It's a firewall issue. The error I'm getting in the logs is lvl=eror msg="Request Completed" method=POST path=/api/ds/query status=500. In the sidebar, hover the cursor over Dashboards (squares) icon, and then click Manage. (I've tried docker-desktop, k3d, and kind, and all of them have the same issue, so I doubt it's the emulator's fault; and I stripped my config down to basically just kube-prometheus, so it's hard to understand where the problem lies, but oh well.). SaveNamePrometheusprometheus . For more detail, feel free to browse the official datasource.yml file example. Using a Client in the same network segment everything works fine and expected. The datasource for the variables was renamed from Telegraf to Telegraf - Dev. [root@kahn.xiao ~]# uname -a We're trying to copy the json from our prod Grafana to our non-prod Grafana, and it shows the following errors. Problem is that I get the error message: This happens with all the dashboards I have imported. Node exporterPromenadeAlertmanagerPrometheusbugbugbug prometheusmysqlmysqlagentmysqld_exporter Grafana throws 'Templating init failed' error after upgrade when using graphite backend, How Intuit democratizes AI development across teams through reusability. rev2023.3.3.43278. By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. e.g. @nirorman Thank you about the answer, it works! Sorry, an error occurred. I would like to see it if possible. Already on GitHub? docker ps To connect the prometheus to GRAFANA, you will need to get the prometheus server IP address that is running as a docker image from host. In fact, you need to use the service_name:port structure. I turned off the firewall on appliance, post that adding http://prometheus:9090 on URL did not throw bad gateway error. 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. Below, youll find a short description of used options: Access mode controls how requests to the data source will be handled. I don't know about the Prometheus Helm-chart, but assuming there is a. Note: By signing up, you agree to be emailed related product-level information. Used with Prometheus Hadoop HDFS FSImage Exporter in kubernetes, Initial dashboard for hadoop in kubernetes (wait what?). In your text editor do a find and replace. I've got two datasource types in the the dashboards (Graphite and Prometheus) and only two data sources configured on the target Grafana instance (set up using the API rather than datasource provisioning). Thanks for contributing an answer to Stack Overflow! "type": "datasource", See error down. With the datasource UID undefined, the graph should now load up as expected. {"err":{"data":null,"status":-1,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"http://:81/metrics/find","params":{"query":"netapp.perf7. Use the Kubernetes-internal IP or domain name. Templating error after exporting to Grafana 4.3.3, http://docs.grafana.org/reference/export_import/. @berghauz thanks. You signed in with another tab or window. , In short, add uid: to your datasource provisioning yaml: This will force Grafana to output all exported dashboards with the uid "myotheruidisanairplane". Sign in prometheus9090node_exporter9100mysqld_exporter9104 To subscribe to this RSS feed, copy and paste this URL into your RSS reader. Also faced with Datasource named ${DS_PROMETHEUS} was not found. Recovering from a blunder I made while emailing a professor. How to notate a grace note at the start of a bar with lilypond? prometheus v2.17.2 via prometheus-operator, grafana v6.7.3 (a04ef6cefc) with prometheus as Data Source, Hadoop 3.1.3 in HA setup ( zookeeper cluster + 3 journalnodes + 3 namenodes, which means 1 active nn and 2 standby). We've closed this issue since it needs more information and hasn't had any activity recently. In other words, you wont have to edit the file manually if you copy the config json from a running Grafana instance that already uses the dashboard: Finally, if you are using my docker-compose.yml file, run the following command to start services: In the grafana service logs I can see that provisioning did not generate any errors: Now, we can visit http://localhost:3000/datasources to see our Prometeus data source: Likewise, go to http://localhost:3000/dashboards to verify that the JVM dashboard is indeed located in the Services directory as we specified in the dashboard.yml file: Next, select the JVM (Micrometer) entry to see the dashboard: What to check when the configuration doesnt work as planned? This repository has been archived by the owner on May 5, 2021. Thanks for contributing an answer to Stack Overflow! Grafana Labs uses cookies for the normal operation of this website. What is the purpose of this D-shaped ring at the base of the tongue on my hiking boots? Thanks for creating this issue! Do new devs get fired if they can't solve a certain bug? In Grafana created two data sources: Test DB (default) and a MySQL named MySQL-1. Asking for help, clarification, or responding to other answers. Another alternative is to open the json file in a a text editor and update the data source properties to value that matches a name of your data source. Reference to what I'm talking about on the Grafana docs: Sounds like youre using template variables. We dont have to manually configure data sources and dashboards for Grafana. Data is present in graphite, but dashboards do not work. Follow the workaround, and find-and-replace all UIDs to be a null-string. Follow the issue template and add additional information that will help us replicate the problem. wizzy download from-gnet dashboard 1471 1 Find the UID that Grafana assigned to the datasource in the JSON. The $ {DS_GRAPHITE} is a variable name from my Grafana configuration and is not recognized by your Grafana server. Grafana throws 'Templating init failed' error after upgrade when using graphite backend Ask Question Asked 5 years, 6 months ago Modified 3 years, 5 months ago Viewed 3k times 6 I'm trying to upgrade my Grafana setup from version v4.0.2 (commit: v4.0.2) to version v4.4.3 (commit: 54c79c5) on CentOS 7. Datasource; 2. Find the UID that Grafana assigned to the datasource in the JSON. Styling contours by colour and by line thickness in QGIS. From: i have exported the dashboard to json to see old datasource references, but there is nothing. Next, we need to mount this configuration to the grafana service. Why do many companies reject expired SSL certificates as bugs in bug bounties? Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2, Posting graphite events to Hosted Graphite, Using Graphite/Grafana for non time based data, Grafana HTTP Error Bad Gateway and Templating init failed errors, Simple percentage in Grafana using graphite, cassandra cluster monitoring using graphite -grafana. Additionally, you can find the detailed description of applying Grafana (v7.1.3) to this project in the How to set up Grafana with Docker and connect it to Prometheus post. ).Best regards,Dan, Your email address will not be published. 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. In the JSON created after the save of my dashboard, I got "datasource": { "type": "datasource", "uid": "grafana" }, , having Prometheus as data source. 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 Any leads on this would be highly appreciated! I've double-checked and graphite is up and running and is listening on the selected URL. How to use Slater Type Orbitals as a basis functions in matrix method correctly? I am facing similar issue? The dashboard JSON is as follows: The template variable seems to be updated correctly, as in the following dashboard JSON. In the meantime you can import the dashboard from grafana.com directly into grafana (which will give you the opportunity to specify the datasource it should use), then import it into wizzy from there. 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. First, download the JSON file using the link provided on the dashboard page: Next, save the file in the grafana/provisioning/dashboards/ directory. All in all, the issue occurs only when working with files downloaded from the Official and community dashboard page. This seems like #11018, also. to your account, What Grafana version are you using? PBFA97CFB590B2093 or it'll be the variable form $ {DS_PROMETHEUS}, which is used when telling Grafana to "Share Externally". 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 Solution is given at #11018 by @torkelo (wish it had been properly documented at the original provisioning docu and in export/import) - { Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. This will work as long as you have both your Grafana and Prometheus running as a docker images so before you begin please run the command below to be sure that both prom and Grafana images are up. Well occasionally send you account related emails. json , 1.1:1 2.VIPC, Grafana json dashboard Templating Failed to upgrade legacy queries Datasource xxx not found, Templating Failed to upgrade legacy queries Datasource xxx not found. This will either look like a random string (e.g. to your account, What happened: Well occasionally send you account related emails. You need to create service monitor on your own. I had the same problem, I didn't know where to get the uid of my data source, so I had to review the request that grafana made to see what information it brought when listing the data sources and I found the valuable UID. Had the same problem with a Graphite-based dashboard. So this dashboard is one that we did not do any manual intervention on and has two variables. The issue is caused by the "datasource": "${DS_PROMETHEUS}" used in the jvm-micrometer_rev9.json file. Dashboard imported without filling template variables and when access those dashboards I see error. Failed to upgrade legacy queries Datasource named $ {DS_PROMETHEUS} was not found and Error updating options: Datasource named $ {DS_PROMETHEUS} was not found I am quite new to Grafana and I haven't been able to find the documentation describing such a situation. Why are Suriname, Belize, and Guinea-Bissau classified as "Small Island Developing States"? Restart Grafana to provision the new dashboard or wait 10 seconds for Grafana to automatically create the dashboard. If you want to import a dashboard from Grafana.com into an older version of Grafana then you can either import it as usual and then update the data source option in the metrics tab so that the panel is using the correct data source. Making statements based on opinion; back them up with references or personal experience. We are trying to render grafana snapshot using an iframe for a dasboard which we are developing. Since Kubernetes uses an overlay network, it is a different IP. To learn more, see our tips on writing great answers. After that , we have created a new datasource Y (influxdb database Y) and change X by Y in all panels 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. https://grafana.com/docs/grafana/latest/http_api/dashboard_versions/#get-dashboard-version, This should give you the dashboard json before the upgrade. Replacing $(DS_PROMETHEUS) with "Prometheus" and making the name of datasource to "Prometheus" in datasources.yaml worked for me in helm charts. I don't think I have a copy handy. What video game is Charlie playing in Poker Face S01E07? Is there a single-word adjective for "having exceptionally strong moral principles"? 5.0.0-beta2, What OS are you running grafana on? Connect and share knowledge within a single location that is structured and easy to search. The text was updated successfully, but these errors were encountered: I'll rename this issue to be about adding support for that. I tried just importing dashboards from grafana's site and hit the same problem. } 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. 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. I imported dashboards with datasources template variables, What was the expected result? I've just tried to apply the workaround mentioned in #11018 but stumbled upon the same issue mentioned in #11018 (comment) - the 'View JSON' export sets the id value to a number which causes Grafana to reject this dashboard when provisioning - it needs to be null (which is set when exporting the dashboard to a file). The Grafana board uses one Postgres source for production and another for non-prod. The URL needs to be accessible from the browser if you select this access mode. Because of it, remember to specify the orgId option accordingly for your data sources if needed. Grafana HTTP Error Bad Gateway and Templating init failed errors, https://kubernetes.io/docs/concepts/services-networking/service/#headless-services, How Intuit democratizes AI development across teams through reusability. Look in the Grafana official site, http://docs.grafana.org/reference/export_import/ in the last paragraph: These inputs and their usage in data source properties are automatically added during export in Grafana 3.1. "Find" your UID from step 2, (. "pluginId": "graphite", Remember, all applications are run with Docker Compose. Your email address will not be published. Sign in @TroldeJens please advise, https://github.com/kiwigrid/k8s-sidecar has env variable Datasource named Prometheus was not found. 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. Is it possible to rotate a window 90 degrees if it has the same length and width? The /etc/grafana/provisionig is the default value in Grafana Docker for the GF_PATHS_PROVISIONING variable. To learn more, see our tips on writing great answers. By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. The URL needs to be accessible from the grafana backend/server if you select this access mode.Browser access mode:All requests will be made from the browser directly to the data source and may be subject to Cross-Origin Resource Sharing (CORS) requirements. Lately, I was configuring provisioning in Grafana 8+ and got the following error: I had to edit the datasource.yml file to get the data source url to contain the appropriate protocol (http in my case): As a result, the url that I got in the Grafana Data Source configuration looks like in the screenshot below: The community dashboards arent always up to date with the Micrometer and Spring releases. This is ridiculous, since I didn't get any warning and everything works fine in the second case. @onemanstartup Dashboards attached to the datasource show up in that tab. I expected to import those dashboards with default value from inputs and fill template variables, What happened instead? Any update on this? At the moment of writing this post the issue seems to be still open. "After the incident", I started to be more careful not to trip over things. In effect, this file will configure a default data source for the default organisation in Grafana (identified with the id=1). 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. Created a query variable using MySQL-1 data source. However, if we are loading it directly in a browser, we are able to see the snap shot getting rendered. We can use one of the predefined, ready to use Grafana dashboards to save time on configuration. Just export -> import does not work in grafana 5.0.4. 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). Grafana v8.4.6 (c53173f), grafana/public/app/features/plugins/datasource_srv.ts. I will try to get this bug fixed in a day or two!