27 Nov
2019
27 Nov
'19
10:02 a.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 9d2023692cc415e061102f2323ab04b78cea4e89
https://github.com/tribe29/checkmk/commit/9d2023692cc415e061102f2323ab04b78…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-11-27 (Wed, 27 Nov 2019)
Changed paths:
A .werks/10412
Log Message:
-----------
10412 FIX Site filter in slave site only holds itself as filter target
Site filter within a customer assigned remote site is quite redundant as
the site only has access to itself, thus never actively used. However, the
filter available targets where poorly listed.
When configuring reports, this site filter aids to establish context for
the report and a poor listing of the single available site(itself) led to
empty results.
CMK-2481
Change-Id: Ie09cb6b7f59c9d0e060577073cbf1648bcbd07cd
Commit: 8f9980b3c771a320adee021cc9abdde06a6e13e0
https://github.com/tribe29/checkmk/commit/8f9980b3c771a320adee021cc9abdde06…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-11-27 (Wed, 27 Nov 2019)
Changed paths:
A .werks/10413
Log Message:
-----------
10413 FIX Sites can not be assigned to global scope
Users can be assigned to configured customers and the provider or to a
global scope to have access to all sites. The same option generators is
used for passwords and sites.
In the case of users and passwords, this objects are available for a
customer or globally. For site the global scope does not make sense as the
site is not available globally, but assigned to a global customer which
doesn't exist. Thus this option is removed to avoid misconfiguration.
Customer valuespec cannot be repeated so easily
Change-Id: Ibfbb85e10ce6644ada17acf84264d17f5be65107
Commit: 7860aa82f742be25f64f24b5ba5a3f6930182572
https://github.com/tribe29/checkmk/commit/7860aa82f742be25f64f24b5ba5a3f693…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2019-11-27 (Wed, 27 Nov 2019)
Changed paths:
A .werks/10411
Log Message:
-----------
10411 Customer specific macro replacements for reporting
Within the customer properties there is now the option to define individual
replacement macros to use in reports. It is possible to set up an arbitrary
number of macros per customer.
Per default, two macros are initiated $CUSTOMER_ID$ and $CUSTOMER_NAME$,
corresponding to the customer properties ID and Name.
CMK-2472
Change-Id: I5f97c008e745d8426956dbbefc658c42f4886145
Compare: https://github.com/tribe29/checkmk/compare/81f9526f472c...7860aa82f742