Service type
Grafana service
Self-hosted Grafana service for dashboards and data visualization using connected data sources.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
On Wodby
How Grafana runs on Wodby
grafana/grafana image and listens on port 3000. Configuration is passed as GF_<SECTION>_<KEY> environment variables, which override the configuration file.What the manifest sets
GF_SERVER_ROOT_URLis the service's URL in the environment.GF_SECURITY_ADMIN_USERandGF_SECURITY_ADMIN_PASSWORDcome from the service tokensadmin_usernameandadmin_password. Grafana applies them once, on the first start with an empty data volume. Changing the tokens later does not change the existing account.- Usage reporting and update checks are off (
GF_ANALYTICS_*).
Data sources
The service can be linked to Grafana Loki, Grafana Tempo, Prometheus and VictoriaMetrics. The links set no variables and create no data source by themselves.
Data sources are declared in the config file "Grafana datasources", mounted at /etc/grafana/provisioning/datasources/wodby.yml. It is empty by default (datasources: []) and has prune: true: a data source removed from the file is deleted from Grafana on the next start. A linked service is reached at http://<its service name>:<its port>, for example port 3100 for Loki, 3200 for Tempo and 8428 for VictoriaMetrics. Grafana reads the file only when it starts: after a change, deploy the service. Wodby restarts Grafana when the file changed.
Changing configuration
Add or change GF_* environment variables on the service, or edit the data sources config file, then deploy. Do not edit grafana.ini in the container: it is not on a volume.
Data
The data volume is mounted at /var/lib/grafana: the built-in SQLite database with dashboards, users and settings, and installed plugins. The manifest declares no backup or import.
Check the result
/api/health on port 3000 reports whether Grafana and its database are up.
Overview
Technical profile and packaging
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Persistent volumes
Stacks
Use it inside ready-made stacks or your own
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains
Volumes
Configs
Service links
These links define which other services can connect to Grafana when it is used inside a stack.
loki
Eligible linked services
prometheus
Eligible linked services
victoria-metrics
Eligible linked services
tempo
Eligible linked services