[checkmk-commits] Check_MK Git: check_mk: BI: Added new column for displaying the numeric state output

Module: check_mk Branch: master Commit: 562e1f559d3fe5bca87c9c11857db673e5636b7c URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=562e1f559d3fe5… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Thu Dec 8 08:44:41 2011 +0100 BI: Added new column for displaying the numeric state output --- .bugs/414 | 10 +++++++--- web/plugins/views/bi.py | 7 +++++++ 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/.bugs/414 b/.bugs/414 index 5f8dcdd..19e1a73 100644 --- a/.bugs/414 +++ b/.bugs/414 @@ -1,11 +1,15 @@ Title: BI: FOREACH_* auch in untergeordneten Ebenen nutzbar machen Component: bi -Benefit: 2 -State: open Cost: 4 Date: 2011-11-24 12:26:52 -Targetversion: future +State: done Class: feature +Benefit: 2 +Fun: 0 +Targetversion: future Um im BI flexibler zu sein, sollte man z.B. FOREACH_SERVICE nicht nur in der obersten Regel-Ebene nutzne können. + +2011-12-08 08:34:39: changed state open -> done +Has been implemented in 1.1.13 code for aggregation rules and services. diff --git a/web/plugins/views/bi.py b/web/plugins/views/bi.py index 2db8c39..8a36060 100644 --- a/web/plugins/views/bi.py +++ b/web/plugins/views/bi.py @@ -74,6 +74,13 @@ multisite_painters["aggr_state"] = { "paint" : lambda row: paint_aggr_state_short(row["aggr_effective_state"], row["aggr_effective_state"] != row["aggr_state"]) } +multisite_painters["aggr_state_num"] = { + "title" : _("Aggregated state (number)"), + "short" : _("State"), + "columns" : [ "aggr_effective_state" ], + "paint" : lambda row: ("", str(row["aggr_effective_state"]['state'])) +} + multisite_painters["aggr_real_state"] = { "title" : _("Aggregated real state (never assumed)"), "short" : _("R.State"),