Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 1e274977c5149781e6ee552dfd5841d0111f2153
https://github.com/tribe29/checkmk/commit/1e274977c5149781e6ee552dfd5841d01…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M tests/git/test_find_debug_print.py
Log Message:
-----------
Simplify tests avoiding debug statements on executable
Change-Id: I61c595dd4213c849c4b5d9a23584261e6244d269
Commit: 72b1c5a0548cf504c6e0066fb4f7b0d94d784b7b
https://github.com/tribe29/checkmk/commit/72b1c5a0548cf504c6e0066fb4f7b0d94…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A bin/update_rrd_fs_names.py
Log Message:
-----------
Script to update rrd info files for new df.include output
Change-Id: I0bbcc4896df13b01785812c29a42a1de5554b9b6
Commit: 9da1057b7479fc8602b36e76e4652ad7959ed104
https://github.com/tribe29/checkmk/commit/9da1057b7479fc8602b36e76e4652ad79…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/7444
M checks/df.include
M cmk/gui/plugins/metrics/check_mk.py
Log Message:
-----------
7444 FIX Rename metric name in Filesystem checks from mount point to fs_used
Filesystem Nagios check plug-in stored the filesystem usage of every mount
points in the RRD databases under the path of each mount point. Checkmk
assigned to every mount point a service, still it kept naming the
filesystem usage with the mount point path for compatibility. Our graphing
system learned to deal with this unpractical convention, however new
features in Checkmk performing bulk access to data can't.
<ul>
<li>All sites created with Checkm 1.6.0 onwards will automatically use the
new naming convention and don't need to be migrated</li>
<li> The migration is not mandatory, your Checkmk instance will continue
working under the legacy mode until you migrate.</li>
<li>If you use CRE, you don't need to de the migration</li>
<li>If you don't plan to do bulk access to data as required by the Historic
Data Views for filesystems (see Werk #7445), you don't need to migrate your
RRD databases.</li>
<li>If you want to use the Historic Data Views for Capacity Management on
Filesystems, you need to do migration.</li>
</ul>
The incorporation of Historic Data Views, for Capacity Management,
requieres querying the filesystem usage of all host in a given time
window. It becomes prohibitive expensive to do such request since first
every service is queried for its mount point name and then every RRD is
individually queried again for the mount point name data.
In this werk we provide a migration script that would edit all meta data
files describing the RRDs that receive output from all our supported
filesystem checks. It will also set a flag in your config so that
Filesystem check plug-ins start delivering usage perfomance data under the
static name of fs_used.
You are advised to do a backup of your RRD files and journal files before
performing the migration and your Checkmk instance needs to be stopped
during the migration.
Migration is one way and needs to be performed once per site any rollback
has to be done from your own backup.
CMK-2261
Change-Id: I0f1f0f7ebfed5053a2d314a83af6f09271259167
Commit: 0a13d17fc050b44e763982eaf77f812299751dcb
https://github.com/tribe29/checkmk/commit/0a13d17fc050b44e763982eaf77f81229…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/7445
Log Message:
-----------
7445 Historic Data Views and Painters for Capacity Management
Capacity management allows you to work with the service metrics historical
data. When configuring a view you can select for a column the "Service
Historic Metrics" option from the drop-down menu, available for the "All
hosts" and "All services" data-sources.
This customizable painter allows you to select, which service metric you
want to analyze, over which time range should data be recovered from your
RRD database, how data is to be consolidated and aggregated. Finally, you
need to label this column to your best convenience.
Some ideas you might want to consider when creating your views:
List all your hosts Peak CPU utilization, over the last week, and also last
month. Maybe you want also to create a new column corresponding to the to
the times a new version of your software was deployed. Time ranges are
completely flexible, and you can keep adding columns for any time window
you prefer.
Analyze over the same time window, the peak, average and minimum CPU
utilization of all your hosts over the last week or last month.
You can also get data from different services at the same time. For example
showing CPU utilization, used memory and disk IO averaged over the last
week.
One last note. Because you will be querying from the RRD data of many hosts
at the same time, query time will increase linearly with the volume of data
you are processing.
Change-Id: Ie7d2d94b2f1c456274c9d793b60ce818144d9279
Compare: https://github.com/tribe29/checkmk/compare/aabe38e6cf94...0a13d17fc050
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: d36ac04be0a09d1aecb7e603cb99ef4b5aa954d2
https://github.com/tribe29/checkmk/commit/d36ac04be0a09d1aecb7e603cb99ef4b5…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M tests/git/test_find_debug_print.py
Log Message:
-----------
Simplify tests avoiding debug statements on executable
Change-Id: I61c595dd4213c849c4b5d9a23584261e6244d269
Commit: a36d4568b7fb0058876a61ecdba0c91a98066d99
https://github.com/tribe29/checkmk/commit/a36d4568b7fb0058876a61ecdba0c91a9…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A bin/update_rrd_fs_names.py
Log Message:
-----------
Script to update rrd info files for new df.include output
Change-Id: I0bbcc4896df13b01785812c29a42a1de5554b9b6
Commit: 3df324c94439e317d32cf0256346ed7965478df8
https://github.com/tribe29/checkmk/commit/3df324c94439e317d32cf0256346ed796…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/7444
M checks/df.include
M cmk/gui/plugins/metrics/check_mk.py
Log Message:
-----------
7444 FIX Rename metric name in Filesystem checks from mount point to fs_used
Filesystem Nagios check plug-in stored the filesystem usage of every mount
points in the RRD databases under the path of each mount point. Checkmk
assigned to every mount point a service, still it kept naming the
filesystem usage with the mount point path for compatibility. Our graphing
system learned to deal with this unpractical convention, however new
features in Checkmk performing bulk access to data can't.
<ul>
<li>All sites created with Checkm 1.6.0 onwards will automatically use the
new naming convention and don't need to be migrated</li>
<li> The migration is not mandatory, your Checkmk instance will continue
working under the legacy mode until you migrate.</li>
<li>If you use CRE, you don't need to de the migration</li>
<li>If you don't plan to do bulk access to data as required by the Historic
Data Views for filesystems (see Werk #7445), you don't need to migrate your
RRD databases.</li>
<li>If you want to use the Historic Data Views for Capacity Management on
Filesystems, you need to do migration.</li>
</ul>
The incorporation of Historic Data Views, for Capacity Management,
requieres querying the filesystem usage of all host in a given time
window. It becomes prohibitive expensive to do such request since first
every service is queried for its mount point name and then every RRD is
individually queried again for the mount point name data.
In this werk we provide a migration script that would edit all meta data
files describing the RRDs that receive output from all our supported
filesystem checks. It will also set a flag in your config so that
Filesystem check plug-ins start delivering usage perfomance data under the
static name of fs_used.
You are advised to do a backup of your RRD files and journal files before
performing the migration and your Checkmk instance needs to be stopped
during the migration.
Migration is one way and needs to be performed once per site any rollback
has to be done from your own backup.
CMK-2261
Change-Id: I0f1f0f7ebfed5053a2d314a83af6f09271259167
Commit: 486da779cf22959da4187e788eee18c0b8f97f7e
https://github.com/tribe29/checkmk/commit/486da779cf22959da4187e788eee18c0b…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/7445
Log Message:
-----------
7445 Historic Data Views and Painters for Capacity Management
Capacity management allows you to work with the service metrics historical
data. When configuring a view you can select for a column the "Service
Historic Metrics" option from the drop-down menu, available for the "All
hosts" and "All services" data-sources.
This customizable painter allows you to select, which service metric you
want to analyze, over which time range should data be recovered from your
RRD database, how data is to be consolidated and aggregated. Finally, you
need to label this column to your best convenience.
Some ideas you might want to consider when creating your views:
List all your hosts Peak CPU utilization, over the last week, and also last
month. Maybe you want also to create a new column corresponding to the to
the times a new version of your software was deployed. Time ranges are
completely flexible, and you can keep adding columns for any time window
you prefer.
Analyze over the same time window, the peak, average and minimum CPU
utilization of all your hosts over the last week or last month.
You can also get data from different services at the same time. For example
showing CPU utilization, used memory and disk IO averaged over the last
week.
One last note. Because you will be querying from the RRD data of many hosts
at the same time, query time will increase linearly with the volume of data
you are processing.
Change-Id: Ie7d2d94b2f1c456274c9d793b60ce818144d9279
Compare: https://github.com/tribe29/checkmk/compare/3434b2364273...486da779cf22
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 95960c903889163a2ea64b5988e7bb2b5be8dc0a
https://github.com/tribe29/checkmk/commit/95960c903889163a2ea64b5988e7bb2b5…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk/utils/labels.py
M cmk_base/discovered_labels.py
M tests/unit/cmk/utils/test_labels.py
M tests/unit/cmk_base/test_discovered_labels.py
Log Message:
-----------
Prepare for discovered service labels
* Add new class ServiceLabel: This represents a service label
in the Checkmk code during execution. This class is meant to
be exposed to the check API. It will be usable in the discovery
function to create a new label like this:
ServiceLabel(u"my_label_key", u"my_value")
* The labels of all services per host are stored in a single file
in the path var/check_mk/discovered_service_labels. This file is
managed by the DiscoveredServiceLabelsStore class.
* During the service discovery in Checkmk base code, the class
DiscoveredServiceLabelsOfHost will be used to collect all discovered
labels and hand them over to DiscoveredServiceLabelsStore for
persistance.
CMK-1816
Change-Id: I918daf1890abe922799485db52a0523228ce3ebf
Commit: fd758f994f7fde613ca4b19f237ea086c59e5364
https://github.com/tribe29/checkmk/commit/fd758f994f7fde613ca4b19f237ea086c…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk/gui/watolib/rulesets.py
M cmk/utils/labels.py
M cmk_base/config.py
M tests/unit/cmk/utils/test_labels.py
M tests/unit/cmk_base/test_config.py
Log Message:
-----------
Export discovered service labels to core
Moved the effective service label calculation to the LabelManager helper
class of the ConfigCache. All discovered labels are now written to the
core configuration which makes them usable in the GUI.
CMK-1816
Change-Id: Id6c93e1a7490518477df5b6cc8adc8d548a68d76
Commit: bf494e994e6cbff1559729a252b5926f23fb9f42
https://github.com/tribe29/checkmk/commit/bf494e994e6cbff1559729a252b5926f2…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/config.py
M cmk_base/discovery.py
Log Message:
-----------
Minor cleanups
* Turn discovery helper functions into iterators
* Add some type annotations and fix some others
CMK-1816
Change-Id: I9d2a2cad17a67ab29044089aa00644cb615ca854
Commit: ec70f81e68cbdc79a53177666fc98c6b689e9dac
https://github.com/tribe29/checkmk/commit/ec70f81e68cbdc79a53177666fc98c6b6…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/check_table.py
M cmk_base/discovery.py
Log Message:
-----------
Wrap discovery results into DiscoveredService objects
Right after receiving the discovered service tuples from the
discovery functions the tuples are validated and converted into
DiscoveredService objects for easier handling in the discovery
function call stack.
Spread a lot of type hints on the way.
CMK-1816
Change-Id: I4fab7754397032a98086ddb75dc1582f3c420f49
Commit: 7e18e61d110d1fe6bcc1ec9370ad152cfc175d3b
https://github.com/tribe29/checkmk/commit/7e18e61d110d1fe6bcc1ec9370ad152cf…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/check_table.py
M cmk_base/discovery.py
Log Message:
-----------
Spread use of DiscoveredService object
Cleanup some unpacking of discovered service attributes into tuples and
use the DiscoveredService objects instead.
CMK-1816
Change-Id: Iafeebd78e48747ec7d361cb5e6a78dd7fe2dadaf
Commit: f736c2f9fd5639f4f3f4da4308a49123d2426e34
https://github.com/tribe29/checkmk/commit/f736c2f9fd5639f4f3f4da4308a49123d…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/discovery.py
Log Message:
-----------
set_autochecks_of: Extract cluster / real host handling
CMK-1816
Change-Id: I603771717330db9bb3408006e9c4673f07308ec0
Commit: e3c2ca11a7991e08e0531d52a393c661f30e08d7
https://github.com/tribe29/checkmk/commit/e3c2ca11a7991e08e0531d52a393c661f…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/automations/check_mk.py
Log Message:
-----------
Host rename: Replace ancient rewrite with simple file rename
Change-Id: Ie90b90f451b4c12853b8d02680b721bf16e8e64e
Commit: 36dcb2f65305fffec7ce1f994d30a26043bb2935
https://github.com/tribe29/checkmk/commit/36dcb2f65305fffec7ce1f994d30a2604…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/automations/check_mk.py
M tests/integration/cmk_base/test_automations.py
M tests/unit/cmk_base/test_unit_automations.py
Log Message:
-----------
Remove ancient get-autochecks automation call
Change-Id: I5670bb5dddf16c9475c11c7235d76530483a8829
Commit: 25a9824585c875dc42cbcc5c5187c66578f26259
https://github.com/tribe29/checkmk/commit/25a9824585c875dc42cbcc5c5187c6657…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/automations/check_mk.py
M cmk_base/check_table.py
M cmk_base/discovery.py
M tests/integration/cmk_base/test_automations.py
M tests/unit/cmk_base/test_autochecks.py
Log Message:
-----------
Spread use of DiscoveredService object
Make autocheck persistance functions also work with the list of
discovered service instead of different specific dict and list
based structures that were all similar, but not exactly the same.
CMK-1816
Change-Id: I311c39db9f8865b472b5da3acb709d9efec346d9
Commit: 88ac3f4f00c033519f7f57d5d07417267c4dc452
https://github.com/tribe29/checkmk/commit/88ac3f4f00c033519f7f57d5d07417267…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/discovery.py
Log Message:
-----------
Simplify discovered services output calculation
Change-Id: Ibad4a32d3860829048315e97bb54a05a7733ba20
Commit: 5a20d1389ff1a3fe6d6259682392a9b8e1a3aeb0
https://github.com/tribe29/checkmk/commit/5a20d1389ff1a3fe6d6259682392a9b8e…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/discovery.py
A tests/unit/cmk_base/test_discovery.py
Log Message:
-----------
Make DiscoveredService comparable to others
This prepares the way to cleanup all the different comparison
data structures during discovered service processing, e.g. used
for preventing duplicate services.
CMK-1816
Change-Id: I9d2b589f6a674e54defc6acd6379d88dc9e79d59
Commit: 82e334c57337d12bd2d7a08c58e962e7883f6b3f
https://github.com/tribe29/checkmk/commit/82e334c57337d12bd2d7a08c58e962e78…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/discovery.py
Log Message:
-----------
Minor cleanup: Reduce nesting
Change-Id: I3f01ecfc8bd0183822173731a0722a1c07a4917e
Commit: 342c0bd4f28341d152758d9592ee2174fce0693d
https://github.com/tribe29/checkmk/commit/342c0bd4f28341d152758d9592ee2174f…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M cmk_base/check_table.py
M cmk_base/discovery.py
M tests/unit/cmk_base/test_autochecks.py
Log Message:
-----------
Autochecks: Use ast parsing instead of hand crafted text parsing
This prepares for parsing more flexible data structures from the
autocheck file while still being able to keep the logic that the
check parameters are not resolved.
CMK-1816
Change-Id: I95cb2deff63f1668253e8fe5671bbf5b9a11142f
Commit: ab6a87faa057fdc80d8244b10288b6c4f2814bf2
https://github.com/tribe29/checkmk/commit/ab6a87faa057fdc80d8244b10288b6c4f…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M tests/unit/cmk_base/test_autochecks.py
Log Message:
-----------
Fix unit test
Change-Id: I6941afe5ab5952cce774442033b1e8ec9d5e70f8
Compare: https://github.com/tribe29/checkmk/compare/afefd2c05a7e...ab6a87faa057
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: c50bc466dd32251866ed0152d51094afd945ba59
https://github.com/tribe29/checkmk/commit/c50bc466dd32251866ed0152d51094afd…
Author: Jonas Kluger <jonas.kluger(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/7928
M checks/zfsget
A tests/unit/checks/generictests/datasets/zfsget_whitespace.py
M tests/unit/checks/test_zfsget.py
Log Message:
-----------
7928 FIX zfsget: whitespace in name discovery bugfix
The check does not crash anymore if a mountpoint/name containes a whitspace. Multiple whitespaces in a mountpoint can now be possible.
Change-Id: I43fd3093911d37a16f72f5ce0fde24647d111d6b
Commit: cb48b52c0acd4877af91850404f73b4604b99915
https://github.com/tribe29/checkmk/commit/cb48b52c0acd4877af91850404f73b460…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
M omd/packages/Python/Python.make
M omd/packages/Python3/Python3.make
M omd/packages/python-modules/python-modules.make
R omd/packages/python-modules/skel/.pip/pip.conf
Log Message:
-----------
Disentangle local pip2/pip3 installation directories.
Previously we used a .pip/pip.conf file to tell pip where to put new
packages, but this single-file approach doesn't work with a parallel
pip2/pip3 installation anymore. Therefore, we patch the pip2/pip3
executable wrappers to set the respective environment variable correctly.
As an added tiny bonus, we disable the annoying pip version check: Updating
pip is not a good recommendation for the site user...
Change-Id: I2c70086d290cadd43b28ca369ead02f5c7a0b9f4
Compare: https://github.com/tribe29/checkmk/compare/ca6ea58e8129...cb48b52c0acd
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 5aeab7ae79f9dc6300bb8a011cfb6af6fa75d995
https://github.com/tribe29/checkmk/commit/5aeab7ae79f9dc6300bb8a011cfb6af6f…
Author: Marcel Arentz <marcel.arentz(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/8801
M checks/oracle_crs_res
M checks/oracle_crs_version
M checks/oracle_crs_voting
Log Message:
-----------
8801 FIX oracle_crs_res, oracle_crs_version, oracle_crs_voting: Fixed error in parameters view
The mentioned checks are not configurable at the moment. Yet the checks
expected a ruleset and gave an error. With this fix the checks are still
not configurable but do not expect to have a corresponding ruleset anymore.
Change-Id: Iafdc93e155b926abc255513d97229e89c8acf9a5
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: ca6ea58e81297b32ce51df86ccf94246394c41b5
https://github.com/tribe29/checkmk/commit/ca6ea58e81297b32ce51df86ccf942463…
Author: Marcel Arentz <marcel.arentz(a)tribe29.com>
Date: 2019-07-15 (Mon, 15 Jul 2019)
Changed paths:
A .werks/8801
M checks/oracle_crs_res
M checks/oracle_crs_version
M checks/oracle_crs_voting
Log Message:
-----------
8801 FIX oracle_crs_res, oracle_crs_version, oracle_crs_voting: Fixed error in parameters view
The mentioned checks are not configurable at the moment. Yet the checks
expected a ruleset and gave an error. With this fix the checks are still
not configurable but do not expect to have a corresponding ruleset anymore.
Change-Id: Iafdc93e155b926abc255513d97229e89c8acf9a5