browbeat/ansible/install/roles/grafana-dashboards/templates/cloud_gnocchi_status.yaml.j2
akrzos c34543f909 Transition to GrafYaml for Dashboard Storage
Reasons to move from json, json.j2 to yaml/yaml.j2 + GrafYaml:
* Yaml is less lines
* Yaml allows comments
* Yaml means less curly braces and quotes
* GrafYaml manages panel ids and target refIds
* GrafYaml defaults reduce number of lines stored
* GrafYaml allows more easily cut/paste management of Dashboards

Identified Downsides:
* GrafYaml will be behind the Grafana Dashboard Model (Until code is updated)
* Json will always allow full feature set
* Installing Dashboards now requires GrafYaml

New Dashboards/Features:
* Templated Dashboards (Reduce line count in "static" dashboards)
* Cloud Specific networks - all dashboard
* Three Node Performance Food groups Enhanced
* Networker Node added for Cloud Specific Dashboards and Total Memory

Change-Id: I55ce9f9f6c28497c8b4ed7a19d42657a8eb14170
2018-02-27 10:20:18 -05:00

22 lines
436 B
Django/Jinja

#jinja2:lstrip_blocks: True
---
dashboard:
title: Cloud Gnocchi Status
templating:
- name: Cloud
query: "*"
refresh: true
type: query
- name: Node
query: "$Cloud.*"
refresh: true
type: query
time:
from: now-1h
to: now
rows:
{% include 'partials/description.yaml' %}
{% set partial_panel = {'collapse': 'false'} %}
{% include 'partials/gnocchi_backlog.yaml.j2' %}