You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can login to Grafana with admin:admin, but it's completely empty. No dashboards or anything like that. The weird thing is that Grafana seems to have everything in there when I'm checking manually in BASH, but nothing loads up on the webpage. If I manually create a datasource or graph on the webpage, I do not see it in the datasources.yml file, I only see the Teslamate file there, however even when I restart Grafana, the datasource I created is still showing up on the webpage, so it must be saved somewhere.
It's almost like it's not using the directory I specified and so not picking up any of the Teslamate stuff, but the log file is saying it is using the correct directory.
I'm using the latest version of Grafana: grafana/grafana:11.5.2
Here's me checking inside the container to ensure files exist:
grafana-teslamate-68f94c794b-745d5:/usr/share/grafana$ ls -ahl /var/lib/grafana/
total 1M
drwxrwx--- 1 grafana 472 264 Mar 15 17:17 .
drwxr-xr-x 1 root root 4.0K Feb 18 21:45 ..
drwxrwx--- 1 grafana 472 362 Mar 15 16:47 @eaDir
-rwxrwx--- 1 grafana 472 1.3K Mar 15 08:06 Dockerfile
-rwxrwx--- 1 grafana 472 679 Mar 15 08:06 apple-touch-icon.png
drwxrwx--- 1 grafana 472 0 Mar 15 17:00 csv
drwxrwx--- 1 grafana 472 594 Mar 15 16:47 dashboards
-rwxrwx--- 1 grafana 472 2.6K Mar 15 08:06 dashboards.sh
-rwxrwx--- 1 grafana 472 714 Mar 15 08:06 dashboards.yml
-rwxrwx--- 1 grafana 472 407 Mar 15 08:06 datasource.yml
-rwxrwx--- 1 grafana 472 473 Mar 15 08:06 favicon.png
-rwxrwx--- 1 grafana 472 1.1M Mar 15 17:17 grafana.db
-rwxrwx--- 1 grafana 472 524 Mar 15 08:06 logo.svg
drwxrwx--- 1 grafana 472 0 Mar 15 17:00 pdf
drwxrwx--- 1 grafana 472 0 Mar 15 17:00 plugins
drwxrwx--- 1 grafana 472 0 Mar 15 17:00 png
grafana-teslamate-68f94c794b-745d5:/usr/share/grafana$ cat /var/lib/grafana/datasource.yml
apiVersion: 1
datasources:
- name: TeslaMate
type: postgres
url: $DATABASE_HOST:$DATABASE_PORT
user: $DATABASE_USER
database: $DATABASE_NAME
access: proxy
basicAuth: false
withCredentials: false
isDefault: true
secureJsonData:
password: $DATABASE_PASS
jsonData:
postgresVersion: 1500
sslmode: $DATABASE_SSL_MODE
version: 1
editable: true
Can you please share your docker-compose.yml without your secrets? Only https://docs.teslamate.org/docs/installation/docker/ is supported. If you are not using the provided Grafana image, the dashboards would not show up. You can try to do a backup and delete the grafana volume.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
alternatively just use our grafana image - it's bundling everything that is needed and ensures provisioned dashboards are tested for the grafana version used.
Is there an existing issue for this?
What happened?
Got a very strange issue.
I can login to Grafana with admin:admin, but it's completely empty. No dashboards or anything like that. The weird thing is that Grafana seems to have everything in there when I'm checking manually in BASH, but nothing loads up on the webpage. If I manually create a datasource or graph on the webpage, I do not see it in the datasources.yml file, I only see the Teslamate file there, however even when I restart Grafana, the datasource I created is still showing up on the webpage, so it must be saved somewhere.
It's almost like it's not using the directory I specified and so not picking up any of the Teslamate stuff, but the log file is saying it is using the correct directory.
I'm using the latest version of Grafana:
grafana/grafana:11.5.2
Here's me checking inside the container to ensure files exist:
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
Screenshots
Additional data
No response
Type of installation
Docker
Version
teslamate:1.32
The text was updated successfully, but these errors were encountered: