feat: promtail loki grafana setup #264
Conversation
tarnas14
force-pushed
the
launchpad/feature/11/promtail_loki_grafana
branch
from
0c9cb20
to
3426d49
Compare
|
|
||
| grafana: | ||
| image: grafana/grafana | ||
| user: "${UID:-root}:${GID:-root}" |
There was a problem hiding this comment.
when starting the docker, we would provide UID and GID env vars
| - ./grafana/sources_provision.yml:/etc/grafana/provisioning/datasources/all.yml # for some reason does not work if volumed into /usr/share/grafana/conf/provisioning/datasources | ||
| - ./grafana/data:/var/lib/grafana | ||
| ports: | ||
| - "3001:3000" |
There was a problem hiding this comment.
it's necessary to expose port 3000 from grafana to embed it in tauri
|
ok, so - this is a working docker-compose with promtail/loki/grafana with provisioned loki |
| networks: | ||
| loki: | ||
|
|
||
| services: |
There was a problem hiding this comment.
possibly loki and promtail will also need persistent volumes for whatever data/db/indexes they create
There was a problem hiding this comment.
This will be hooked into the launchpad container setup. We could create volumes for these, sure.
| promtail: | ||
| image: grafana/promtail | ||
| volumes: | ||
| - ~/.cache/tari/tmp/:/var/log |
There was a problem hiding this comment.
this volume definition needs to change depending on OS - promtail config file assumes logs in /var/log, but different host directories will have to be mounted per OS
There was a problem hiding this comment.
Yeah. Again, the docker-compose file will be superceded by launchpad, which can dynamically configure these things
| cookie_samesite = lax | ||
|
|
||
| # set to true if you want to allow browsers to render Grafana in a <frame>, <iframe>, <embed> or <object>. default is false. | ||
| allow_embedding = true |
There was a problem hiding this comment.
this is the most important change in comparison to a default defaults.ini
(and the only one)
| networks: | ||
| loki: | ||
|
|
||
| services: |
There was a problem hiding this comment.
This will be hooked into the launchpad container setup. We could create volumes for these, sure.
| promtail: | ||
| image: grafana/promtail | ||
| volumes: | ||
| - ~/.cache/tari/tmp/:/var/log |
There was a problem hiding this comment.
Yeah. Again, the docker-compose file will be superceded by launchpad, which can dynamically configure these things
|
Yes, exactly. |
Description
run with
docker-compose -f docker-compose.grafana.yml up -d(you might need to change volume in docker-compose if running on macOS)
Motivation and Context
#11
How Has This Been Tested?