href: "#nodata"

Hipchat room, or whoever is 'oncall' in Pagerduty.

<p>Two subtabs will appear, 'Triggered Alerts' and 'Manage Metric Alerts'.

<li>Choose the average, minimum, maximum, or sum of a metric over specific hosts,

<li>Choose a simple or multi alert; <a href="#simple">multi-alerts</a> are flexible

<li>Set the alert conditions; if the metric was above or below a threshold value on average,

<p>When setting the alert conditions, ensure that the threshold value you use correctly

matches the unit that are showing in the graph (for example, bytes vs GB). The

'on average' option updates each minute to include the most recent time and dropoff

<h4 id="autoresolve">Autoresolving alerts</h4>

<img src="/static/images/alert_auto.png" style="width:100%; border:1px solid #777777"/>

<p>In the final step of setting up an alert, you can give any necessary commentary

for the alert so if it triggers it will alert the correct people with the most context possible.

Each graph delivered via email or in the event stream when an alert triggers is a hyperlink

to that graph at that exact timeframe. In the body of the message you can <a href="/faq/#notify">@notify</a>

members of the team to have it specifically call out to them. You can also do this in

<li>Can you alert on an event? Not currently, but we're discussing how we'd like to implement this.

As an alternative you can set up an @ notification in the body of the event which would deliver the

---

title: Guide to Dashboard Templating

sidebar:

nav:

- header: Guide to Templating

- text: Enabling dashboard templating

href: "#new"

- text: Defining template variables

href: "#def"

- text: Using template variables in graph editors

href: "#graph"

---

<p>Dashboard templating allows you to create dashboards that use variables like <code>$scope</code> or <code>$redis</code> in place of specific tags or hosts. Dynamically explore the same metrics across different sets of tags by selecting new variable values, without switching through multiple dashboards or changing graph and widget definitions.</p>

<h3 id="new">Enabling dashboard templating</h3>

<p>To create a new templated dashboard, select the 'Use templated sources for metrics'

checkbox in the dashboard creation menu.</p>

<img src="/static/images/template_new_dash.png" style="width:100%; border:1px solid #777777" />

<p>To add templating to an existing dashboard, click the 'Toggle Templating' icon in an existing dashboard.</p>

<img src="/static/images/toggle_templating.png" style="width:100%; border:1px solid #777777" />

<h3 id="def">Defining new template variables</h3>

<img src="/static/images/redis-tpl-panel.png" style="width:100%; border:1px solid #777777" />

<p>A template variable is defined by a name and optional parameters for 'Tag Group' and 'Default Tag.' A tag group is a prefix shared among several tags, like <code>redis_port</code> for the tags <code>redis_port:6379</code> and <code>redis_port:6280</code>. Setting a tag group eliminates irrelevant tags from the variable's scope selector.

The 'Default Tag' option determines the initial value for the variable on dashboard load.</p>

<h3 id="graph">Using template variables in graph editors</h3>

<img src="/static/images/redis-tpl-graph-editor.png" style="width:70%; border:1px solid #777777" />

<p>Once defined, template variables appear alongside normal tag and host options in graph editors. If you set <code>redis_port:6379</code> as the value of <code>$redis</code>, all graphs defined with <code>$redis</code> will be scoped to <code>redis_port:6379</code>.

<img src="/static/images/redis-tpl-selector.png" style="width:70%; border:1px solid #777777" />

<li><a href="/guides/templating/">Guide to Dashboard Templating</a></li>