Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 12d580b82342b4daf3f428912690b1447e134c69
https://github.com/tribe29/checkmk/commit/12d580b82342b4daf3f428912690b1447…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
M cmk/utils/observer.py
A tests/unit/cmk/utils/test_observer.py
Log Message:
-----------
SUP-5782: introduce FetcherMemoryObserver as fetcher watchdog
- implement FetcherMemoryObserver as a subclass from AbstractMemoryObserver
- add unit tests
The CL had been tested manually using absurdly low value to simulate memory overload to confirm that Microcore does restart of Fetcher on fetcher exit.
This CL provides only basic watchdog functionality for bin/fetcher.
Some other features, like logging, will be implemented with separate CL;s
Change-Id: I301ce844df31958e2976e1e3f3160a7928ad209b
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 3393a2b37469c77a598f0343d4b475fcc27422f8
https://github.com/tribe29/checkmk/commit/3393a2b37469c77a598f0343d4b475fcc…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12320
M cmk/base/config.py
M tests/unit/cmk/lib/test_snmplib_snmp_table.py
Log Message:
-----------
SUP-5782: fix memory leak forcing CLASSIC SNMP backend for any host using SNMP-v1
- return CLASSIC backend for SNMP-v1 host
- test functionality
- refactor a bit HostConfig to make the fix testable
- werk
NOTE: This kind of cherry pick from master.
Motivation
1. Memory leak is quite serious problem even being controlled with MemoryObserver(still todo). De-facto it is show stopper at least for some of our clients.
2. We can't fix netsnmp memory leak quick enough due to complexity of the task. There is small probability that we could not fix netsnmp at all.
The fix provides reasonable still temporary by nature workaround to win time for development appropriate solution.
Change-Id: I2c3341d7826375859d9ebac58d0a627ab938752b
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 15b4095498ab4cd5cbc8ed3755a6124a7f176f72
https://github.com/tribe29/checkmk/commit/15b4095498ab4cd5cbc8ed3755a6124a7…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12483
M cmk/gui/plugins/metrics/check_mk.py
Log Message:
-----------
12483 Event rates in graphs can be of very small magnitude
Event rates were displayed with at most a presision of 2 decimals on the
graphs, and was generally a good format. Yet, there are some cases when
monitoring very sporadic events, graphs would show a scale containing only
zeros.
After this werk, event rates follow the same scientific notation used on
other metrics like floating point numbers, counts and percent. This allows
to appropiately display numbers regardless of their domain range.
SUP-5671
Change-Id: Iac3839115327186d4fdfa16947d4c912237aa404
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: e1b14fb50218eaa0a5f9e0c380b9f2afdde4712f
https://github.com/tribe29/checkmk/commit/e1b14fb50218eaa0a5f9e0c380b9f2afd…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12484
Log Message:
-----------
12484 FIX Fix customgraphs in reports
Customgraph report elements cause an exception. This is now fixed
Change-Id: Id2e476e802085b9bce227197beb910b35893af45
Commit: f806fdbc9911d336945ee39a3de449bbd35f5123
https://github.com/tribe29/checkmk/commit/f806fdbc9911d336945ee39a3de449bbd…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12483
M cmk/gui/plugins/metrics/unit.py
Log Message:
-----------
12483 Event rates in graphs can be of very small magnitude
Event rates were displayed with at most a presision of 2 decimals on the
graphs, and was generally a good format. Yet, there are some cases when
monitoring very sporadic events, graphs would show a scale containing only
zeros.
After this werk, event rates follow the same scientific notation used on
other metrics like floating point numbers, counts and percent. This allows
to appropiately display numbers regardless of their domain range.
Change-Id: Iac3839115327186d4fdfa16947d4c912237aa404
Compare: https://github.com/tribe29/checkmk/compare/7a3dabade9d7...f806fdbc9911
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 5a86998cca7eb9f74e30cb7398e0ae0e52d9c11d
https://github.com/tribe29/checkmk/commit/5a86998cca7eb9f74e30cb7398e0ae0e5…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12483
M cmk/gui/plugins/metrics/unit.py
Log Message:
-----------
12483 Event rates in graphs can be of very small magnitude
Event rates were displayed with at most a presision of 2 decimals on the
graphs, and was generally a good format. Yet, there are some cases when
monitoring very sporadic events, graphs would show a scale containing only
zeros.
After this werk, event rates follow the same scientific notation used on
other metrics like floating point numbers, counts and percent. This allows
to appropiately display numbers regardless of their domain range.
Change-Id: Iac3839115327186d4fdfa16947d4c912237aa404
Commit: 3cf3718c340110a812cd3d345e4e7bd1643ccd11
https://github.com/tribe29/checkmk/commit/3cf3718c340110a812cd3d345e4e7bd16…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12484
Log Message:
-----------
12484 FIX Fix customgraphs in reports
Customgraph report elements cause an exception. This is now fixed
Change-Id: Id2e476e802085b9bce227197beb910b35893af45
Compare: https://github.com/tribe29/checkmk/compare/cec82894a774...3cf3718c3401
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: cec82894a7745a73e4034d4686a66e9bba431724
https://github.com/tribe29/checkmk/commit/cec82894a7745a73e4034d4686a66e9bb…
Author: Wontek Hong <wontek.hong(a)tribe29.com>
Date: 2021-04-08 (Thu, 08 Apr 2021)
Changed paths:
A .werks/12692
M checks/k8s_replicas
Log Message:
-----------
12692 FIX k8s_replicas: proper check message when replicas data is not available
In some instances, the Kubernetes replicas information is either incomplete or
not available. The unavailability is usually of short period. This werk introduces
a proper check message which is shown when this event arises. In the previous version,
this scenario was left unhandled and resulted in the check failing.
Change-Id: I9e78f3de3ffd800cf0b78c4ed7d50818f3a73495