Skip to content


A template defines what kind of data a graph visualizes, which kind of graph to use and its style. Essentially the Icinga Web Graphite Integration is using templates to tell Graphite how to render which graphs.

Template Location

There are a bunch of templates already included, located in the installation path. (e.g. /usr/share/icingaweb2/modules/graphite)

To add additional/customized templates, place them in its configuration path. (e.g. /etc/icingaweb2/modules/graphite/templates) These will either extend the available templates or override some of them. Subfolders placed here will also be included in the same way, while additionally extending or overriding templates of its parent folders.


Hidden files and directories (with a leading dot) are ignored.

Template Structure

Templates are organized within simple INI files. However, it is perfectly valid to define multiple templates in a single file.

The name of a section consists of two parts separated by a dot:


The first part is the name of the template and the second part the name of one of the following configuration topics:


Template file will be ignored if the [graph] or [metric_filters] section is missing.

Template Structure: graph

Supports a single option called check_command and should be set to the name of a Icinga 2 check-command. To get multiple graphs for hosts and services with this check-command, multiple templates can reference the same check-command.

If multiple check commands do effectively the same thing and yield the same perfdata, all of them may be specified separated by comma. E.g.:

check_command = "ping, ping4, ping6"

Template Structure: metric_filters

Define what metric to use and how many curves to display in the resulting graph. Each option’s key represents the name of a curve. Its value the path to the metric in Icinga 2’s graphite naming schema.

Curve names are used to map Graphite functions to metrics. (More on this below) However, they are fully arbitrary and have no further meaning outside template configurations.

A curve’s metric path must begin with either the macro $host_name_template$ or $service_name_template$ and is substituted with Icinga 2’s prefix label. The rest of the path is arbitrary, but to get meaningful results use a valid path to one of the performance data metrics:


An example path which points to the metric value of the rta perfdata-label looks as follows:


To dynamically render a graph for each performance data label found, define a macro in place for the actual perfdata-label:


You can also use wildcards. To define a wildcard, please use the following syntax:

$macro:wildcard syntax here$

Some Examples:



The name of the macro for the perfdata-label is also arbitrary. You may as well use a more descriptive name such as $disk$ for the disk check. $disk$ is the same as $disk:*$.

Template Structure: urlparams

Allows to define additional URL parameters to be passed to Graphite’s render API.

Each option represents a single parameter’s name and value. A list of all supported parameters can be found here.

If you have used a macro for the curve’s perfdata-label you may utilize it here as well:

title = "Disk usage on $disk$"

You may also define URL parameters once for all templates (including the shipped ones) in the default_url_params section in /etc/icingaweb2/modules/graphite/config.ini:

yUnitSystem = "none"

These may be overridden in the template itself:

yUnitSystem = "binary"

Template Structure: functions

Allows to define Graphite functions which are applied to the metric of a specific curve on the graph.

Each option’s key must match a curve’s name in order to apply the function to the curve’s metric. A list of all supported functions can be found here.

The metric in question can be referenced in the function call using the macro $metric$ as shown in the following example:

alias(color(scale($metric$, 1000), '#1a7dd7'), 'Round trip time (ms)')

In addition you may utilize all other macros here as well:

alias(color(scale(divideSeries($metric$, $service_name_template$.perfdata.$disk$.max), 100), '#1a7dd7'), 'Used (%)')

Template Example

The configuration examples used in this document are borrowed from the template for the hostalive check-command:

check_command = "hostalive"

rta.value = "$host_name_template$.perfdata.rta.value"

areaAlpha = "0.5"
areaMode = "all"
min = "0"
yUnitSystem = "none"

rta.value = "alias(color(scale($metric$, 1000), '#1a7dd7'), 'Round trip time (ms)')"

check_command = "hostalive"

pl.value = "$host_name_template$"

areaAlpha = "0.5"
areaMode = "all"
min = "0"
yUnitSystem = "none"

pl.value = "alias(color($metric$, '#1a7dd7'), 'Packet loss (%)')"

Default Template Settings

Next to maintaining templates for specific commands, you can specify the default template settings in the default.ini configuration file.

The following example adjusts the background and foreground colors to setup the “dark mode” for graphs.

First, copy the package provided configuration into the configuration path. Then add the bgcolor and fgcolor settings into the urlparams sections for default-host and default-service.

cp /usr/share/icingaweb2/modules/graphite/templates/default.ini /etc/icingaweb2/modules/graphite/templates/default.ini

vim /etc/icingaweb2/modules/graphite/templates/default.ini


bgcolor = "black"
fgcolor = "white"


bgcolor = "black"
fgcolor = "white"

The settings make use the urlparams section which adds the parameters to the render API.


Instead of modifying the color settings in the default template, you can also change the Graphite configuration explained in this community topic.

Further reading