-
Notifications
You must be signed in to change notification settings - Fork 28
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
Local file paths fail #37
Comments
I ran also into this issue; |
Hi @Ognian, can you confirm that this is the log line you're seeing:
Could you share some details on plugin version, Grafana version, and the OS you're running Grafana on? Local means a file on the server. Would a description next to the button help here, or do you think we should call it something else? |
Hi @marcusolsson, |
Hello everyone, I know this is closed
Solution (inspired by local csv related topics in "discussion"): moving some_folder and below to /usr/share/grafana/public/ mv /home/my_user/some_folder /usr/share/grafana/public/ now the (new) local path HTH, ps. maybe that "right" part (777) ps2. versions: |
That works for me on a airgapped raspberrypi 2! Thank you @yaga8795 |
Shouldn't this get published on the documentation page? Setup the data source as: /usr/share/grafana/public/ Good notes in this issue! |
Some users have reported errors when loading local files:
From the log lines in this comment, it seems like Grafana is trying to parse the local file path it as a URL.
The plugin does use the URL field in the data source config to store the file path since that's only way to display the path in the data source list. You can see this by switching between HTTP and Local.
My initial thought was that recent versions of Grafana had introduced additional validation for the URL field. Unfortunately, I seem to be unable to reproduce this on my machine. I've tried both Brave and Safari, for the following versions:
I'd like to figure out under what circumstances this happens. If not, I'll have to stop reusing the URL field for the file path. This will make it hard to find the right data source from the list though.
The text was updated successfully, but these errors were encountered: