92ef419c01
Added with dd6582e9ccb2b5fcb31e3833166df3af5aec9eff, we have found that setting a bool here means the query variable no longer refreshes at all. Thus it's dangerous to accept it, force it to be an int. For reference, the values seem to be 0 = never refresh 1 = on load 2 = on timeseries change Change-Id: Ia96f0166a80ece0b307acdca20eeca045a2e4a75
grafyaml
At a glance
- Free software: Apache license
- Documentation: http://docs.openstack.org/infra/grafyaml/
- Source: http://git.openstack.org/cgit/openstack-infra/grafyaml
- Bugs: https://storyboard.openstack.org/#!/project/818
Overview
grafyaml takes descriptions of Grafana dashboards in YAML format, and
uses them to produce JSON formatted output suitable for direct import
into Grafana.
The tool uses the Voluptuous data validation library to ensure the input produces a valid dashboard. Along with validation, users receive the benefits of YAML markup such as comments and clearer type support.
For example, here is a minimal dashboard specification
dashboard:
time:
from: "2018-02-07T08:42:27.000Z"
to: "2018-02-07T13:48:32.000Z"
templating:
- name: hostname
type: query
datasource: graphite
query: node*
refresh: true
title: My great dashboard
rows:
- title: CPU Usage
height: 250px
panels:
- title: CPU Usage for $hostname
type: graph
datasource: graphite
targets:
- target: $hostname.Cpu.cpu_prct_usedgrafyaml can be very useful in continuous-integration
environments. Users can specify their dashboards via a normal review
process and tests can validate their correctness.
A large number of examples are available in the OpenStack project-config repository, which are used to create dashboards on http://grafana.openstack.org.