Grafana datasources#
This page lists the datasources the stack provisions in Grafana and the settings of the dashboard sidecar. Dashboards reference a datasource by its UID.
Provisioned datasources#
The stack provisions all datasources through grafana.datasources in the kube-prometheus-stack values.
The datasource sidecar is disabled, and so is the chart’s default Prometheus datasource.
Name |
Type |
UID |
URL |
Default |
|---|---|---|---|---|
|
|
|
|
yes |
|
|
|
|
no |
|
|
|
|
no |
|
|
|
|
no |
|
|
|
|
no |
<namespace> is the value of namespace in the configuration.
The Tempo datasource exists only when tempo.enabled is true.
Datasource settings#
ThanosandPrometheustimeInterval: 30s.Alertmanagerimplementation: prometheusandhandleGrafanaManagedAlerts: false.LokimaxLines: 1000. The provisioning deletes any existing datasource namedLokiin organization1before it creates the datasource with UIDloki.Tempotimeout: 60.tracesToLogsV2points at the datasource UIDloki, filters by trace ID, and shifts the time range by one hour in each direction.tracesToMetricspoints at the datasource UIDthanos.
Dashboard sidecar#
The Grafana dashboard sidecar loads every ConfigMap that carries the label grafana_dashboard: "1".
Setting |
Value |
|---|---|
|
|
|
|
|
|
A dashboard ConfigMap with the annotation grafana_folder lands in the Grafana folder of that name.
A dashboard ConfigMap without the annotation lands in the folder General.
Grafana server#
Setting |
Value |
|---|---|
|
|
|
|
Ingress |
Created unless |
Persistence |
|
See also#
Add application dashboards and alerts — how to ship a dashboard to the sidecar.
Embed Grafana in another application — how to allow framing of Grafana.
Configuration options — every configuration field.