Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: edef8f25cd501e1a716f1f3b43227fb1c8feb8b1
https://github.com/tribe29/checkmk/commit/edef8f25cd501e1a716f1f3b43227fb1c…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
M cmk/gui/plugins/dashboard/single_metric.py
M web/htdocs/js/modules/figures/cmk_figures.js
M web/htdocs/js/modules/figures/cmk_gauge.js
M web/htdocs/js/modules/figures/cmk_timeseries.js
Log Message:
-----------
Background Color for single metric based on metric state
- Display of metric value, in neutral color, matching metric state, or
having background match metric state
- When background coloring is selected change the metric color for the
historic values to the status color with different opacity
- Need to reorder levels array crit range first, so that find works in
convention crit at, warn at and still does not crash with max==crit==value
- Refactor collect renderable_value function for processing the main value
on Dashlet single metric and gauge
- Refactor split_unit only to worry about formatted value, no extra properties
- Refactor to reuse commonalities between subplot area and line
- Configuration is not explicit about "area" and "line", instead of true/false
- Single metric draw area stroke only on top border, as an extra styling
CMK-6223
Change-Id: Ida37cb17a3f792d5939ed02af2fcbff501e4014f
Commit: 2f021becc099e3c65b7aeab155146447e8ff408e
https://github.com/tribe29/checkmk/commit/2f021becc099e3c65b7aeab155146447e…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
M cmk/gui/plugins/dashboard/single_metric.py
M web/htdocs/js/modules/figures/cmk_timeseries.js
Log Message:
-----------
Set fix styling of single metric with history
- Default blue on metric and always area plot
- No grid in dashlet
Change-Id: I4923033a857e30b43403178dc07d92b7e12e61fd
Compare: https://github.com/tribe29/checkmk/compare/f323c45fec6f...2f021becc099
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: f323c45fec6f2b4f223af2cde7787629487ddd47
https://github.com/tribe29/checkmk/commit/f323c45fec6f2b4f223af2cde77876294…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/11352
M checks/iptables
Log Message:
-----------
11352 FIX iptables: Keep ACK after update/restart
In case a changed iptable config - which results in {CRIT} - was acknowledged, the ACK vanished after a <tt>omd update<\tt> or <tt>omd restart<\tt>.
The reason therfore is that the check will go to state {OK} for one checkinterval after the update/restart and then become {CRIT} again.
The intermediate state is now {PENDING}, which is actually more precise.
Change-Id: If79680696ea85c36d894d9b5babba09e41312a8c
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: c991de0698a5536a2cdc154043b9265be8bc9cb8
https://github.com/tribe29/checkmk/commit/c991de0698a5536a2cdc154043b9265be…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12041
M cmk/gui/plugins/views/icons/builtin.py
Log Message:
-----------
12041 FIX Fix broken host graphs on views with some joined service columns
CMK-6640
Change-Id: I08b9327de2b65a2c98be7bc5492cba9e0b972c81
Commit: e2210a814a4cbcc6140e6d77cdc6c6fc9a744831
https://github.com/tribe29/checkmk/commit/e2210a814a4cbcc6140e6d77cdc6c6fc9…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12038
M cmk/gui/dashboard.py
M cmk/gui/plugins/dashboard/utils.py
M tests/unit/cmk/gui/plugins/dashboard/test_dashboard_utils.py
Log Message:
-----------
12038 FIX Fix displaying host graphs on dashboard
Previous 2.0.0 versions could not display host related time series graphs on
the dashboard. The new context validation mechanism, that expects a service
context for this dashlet, was preventing the rendering of that dashlet. Now
the host dashlets automatically get an empty service context set which makes
the dashlet render again.
Change-Id: I8a443775117dced2a878f757aa2c8693409df750
Commit: 2cddb3151c1c6fc425c0fa4583e9077bd02c9f76
https://github.com/tribe29/checkmk/commit/2cddb3151c1c6fc425c0fa4583e9077bd…
Author: Ronny Bruska <ronny.bruska(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
M cmk/gui/htmllib.py
M cmk/gui/valuespec.py
M web/htdocs/js/modules/valuespecs.js
Log Message:
-----------
Render emblem as icon image in IconSelector
CMK-6019
Change-Id: I27d8ac576e3bcb0638e4786f45d52b99a16bd062
Compare: https://github.com/tribe29/checkmk/compare/1e3f1402d2f3...2cddb3151c1c
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 6b4449601cc59507477b2fccf90e5d30953612bf
https://github.com/tribe29/checkmk/commit/6b4449601cc59507477b2fccf90e5d309…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12041
M cmk/gui/plugins/views/icons/builtin.py
Log Message:
-----------
12041 FIX Fix broken host graphs on views with some joined service columns
CMK-6640
Change-Id: I08b9327de2b65a2c98be7bc5492cba9e0b972c81
Commit: ccdeef47f90469cfcef7f7fa0a0ebbd64be42d3f
https://github.com/tribe29/checkmk/commit/ccdeef47f90469cfcef7f7fa0a0ebbd64…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12038
M cmk/gui/dashboard.py
M cmk/gui/plugins/dashboard/utils.py
M tests/unit/cmk/gui/plugins/dashboard/test_dashboard_utils.py
Log Message:
-----------
12038 FIX Fix displaying host graphs on dashboard
Previous 2.0.0 versions could not display host related time series graphs on
the dashboard. The new context validation mechanism, that expects a service
context for this dashlet, was preventing the rendering of that dashlet. Now
the host dashlets automatically get an empty service context set which makes
the dashlet render again.
Change-Id: I8a443775117dced2a878f757aa2c8693409df750
Compare: https://github.com/tribe29/checkmk/compare/bde519b809d4...ccdeef47f904
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: bde519b809d487b97fc443c5d94193649a534684
https://github.com/tribe29/checkmk/commit/bde519b809d487b97fc443c5d94193649…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/11352
M checks/iptables
Log Message:
-----------
11352 FIX iptables: Keep ACK after update/restart
In case a changed iptable config - which results in {CRIT} - was acknowledged, the ACK vanished after a <tt>omd update<\tt> or <tt>omd restart<\tt>.
The reason therfore is that the check will go to state {OK} for one checkinterval after the update/restart and then become {CRIT} again.
The intermediate state is now {PENDING}, which is actually more precise.
Change-Id: If79680696ea85c36d894d9b5babba09e41312a8c
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: f268e12c649ceef47d597ca6bb2cdf0265d9007c
https://github.com/tribe29/checkmk/commit/f268e12c649ceef47d597ca6bb2cdf026…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/11352
M checks/iptables
Log Message:
-----------
11352 FIX iptables: Keep ACK after update/restart
In case a changed iptable config - which results in {CRIT} - was acknowledged, the ACK vanished after a <tt>omd update<\tt> or <tt>omd restart<\tt>.
The reason therfore is that the check will go to state {OK} for one checkinterval after the update/restart and then become {CRIT} again.
The intermediate state is now {PENDING}, which is actually more precise.
Change-Id: If79680696ea85c36d894d9b5babba09e41312a8c
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: cca9c5c2d0d3795220b5c086a297d12c19fc5c9f
https://github.com/tribe29/checkmk/commit/cca9c5c2d0d3795220b5c086a297d12c1…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12037
M cmk/gui/watolib/activate_changes.py
Log Message:
-----------
12037 FIX Fix dynamic configuration executing only phase 1 in some distributed setups
Since werk #11972 (2.0.0b5) some dynamic configuration connections in
distributed setups were only executing phase 1 of the dynamic configuration.
As a result the connections were not creating new hosts anymore.
Change-Id: If6fda65e6629eafa0171250a8945f8ad1ec2e6b5
Commit: abc305157f2ef0943f8a85656e8116e97d93d005
https://github.com/tribe29/checkmk/commit/abc305157f2ef0943f8a85656e8116e97…
Author: Joerg Herbel <joerg.herbel(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
M .werks/12020
Log Message:
-----------
Fix version of werk #12020
Change-Id: I85ba7cc13f3537fc3c1545cae3438fedc3f3a432
Compare: https://github.com/tribe29/checkmk/compare/789be7bf7d2e...abc305157f2e
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 1e3f1402d2f3900a21643b65479d8c484a6f308e
https://github.com/tribe29/checkmk/commit/1e3f1402d2f3900a21643b65479d8c484…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2021-02-04 (Thu, 04 Feb 2021)
Changed paths:
A .werks/12037
M cmk/gui/watolib/activate_changes.py
Log Message:
-----------
12037 FIX Fix dynamic configuration executing only phase 1 in some distributed setups
Since werk #11972 (2.0.0b5) some dynamic configuration connections in
distributed setups were only executing phase 1 of the dynamic configuration.
As a result the connections were not creating new hosts anymore.
Change-Id: If6fda65e6629eafa0171250a8945f8ad1ec2e6b5