• {{targetLetters[$index]}}
  • Cache timeout
  • Max data points
Shorter legend names
  • alias() function to specify a custom series name
  • aliasByNode(2) to alias by a specific part of your metric path
  • aliasByNode(2, -1) you can add multiple segment paths, and use negative index
  • groupByNode(2, 'sum') is useful if you have 2 wildcards in your metric path and want to sumSeries and group by
Series as parameter
  • Some graphite functions allow you to have many series arguments
  • Use #[A-Z] to use a graphite query as parameter to a function
  • Examples:
    • asPercent(#A, #B)
    • prod.srv-01.counters.count - asPercent(#A) : percentage of count in comparison with A query
    • prod.srv-01.counters.count - sumSeries(#A) : sum count and series A
    • divideSeries(#A, #B)
  • If a query is added only to be used as a parameter, hide it from the graph with the eye icon
Stacking
  • You find the stacking option under Display Styles tab
  • When stacking is enabled make sure null point mode is set to 'null as zero'
Templating
  • You can use a template variable in place of metric names
  • You can use a template variable in place of function parameters
  • You enable the templating feature in Dashboard settings / Feature toggles
Max data points
  • Every graphite request is issued with a maxDataPoints parameter
  • Graphite uses this parameter to consolidate the real number of values down to this number
  • If there are more real values, then by default they will be consolidated using averages
  • This could hide real peaks and max values in your series
  • You can change how point consolidation is made using the consolidateBy graphite function
  • Point consolidation will effect series legend values (min,max,total,current)
  • If you override maxDataPoint and set a high value performance can be severely effected