App service
Services/Grafana

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

What Wodby sets up for Grafana on this service. It runs from the official 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_URL is the service's URL in the environment.
  • GF_SECURITY_ADMIN_USER and GF_SECURITY_ADMIN_PASSWORD come from the service tokens admin_username and admin_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

This page shows how Grafana is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

13.2

Ports and protocols

3000/HTTP

Labels

grafana, monitoring, visualization

Persistent volumes

Grafana data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Grafana as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

3000/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Volumes

Grafana data

Configs

1 config can be versioned with the service.

Service links

These links define which other services can connect to Grafana when it is used inside a stack.