Plugins state_warning and state_critical not detected with munin-httpd

[quentin-st]

While graphs in generated HTML files contains a special class when they have a warning/critical state, munin-httpd doesn't seems to detect it.

In the munin-nodeview.tmpl, we print an "iwarn" or "icrit" class on the graphs when needed. It seems that STATE_WARNING and STATE_CRITICAL attributes for each SERVICE loop element always returns false.

How to reproduce: trigger a critical state for any plugin, or create a fake one:

#!/bin/bash

case $1 in
    config)
        cat <<'EOM'
graph_title Errors plugin
graph_vlabel n_errors
graph_category tests
graph_scale no
graph_info This is a fake plugin which always produces an error level warning.
n_errors.label n_errors
n_errors.warning 2
n_errors.critical 4
n_errors.info Triggers the error. Its value is always 5.
EOM
        exit 0;;
esac

printf "n_errors.value 5"

[quentin-st]

Also, a plugin in a warning or critical state isn't shown in the left navigation menu ("Criticals (0)"), so it doesn't seem to be specific to the template.

[quentin-st]

It seems that it doesn't come from HTML.pm neither. I tried to run the query on a SQL dump: the ds.warning and ds.critical field both has a 0 value.

Here's the query:

SELECT ds.name, ds.warning, ds.critical FROM service
INNER JOIN ds ON ds.service_id = service.id
WHERE service.name = 'crit_plugin' OR service.name = 'warn_plugin'

And here's the result:

name     | warning   | critical
n_warn   | 0         | 0
n_crit   | 0         | 0