ID: 3294
Title: Fixed mixed languages when some users have localized GUI and some not
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.9i1
When some of the GUI users are using a localized GUI and some are at the default
setting (have no explicit language configured), it could happen that the later
users sometimes see the GUI in the language another user has configured.
ID: 3013
Title: Inventory: snmp inventory plugins never use cached data
Component: HW/SW-Inventory
Level: 1
Class: Bug Fix
Version: 1.2.9i1
This fixes a bug where inventory data from snmp devices
got cached indefinitely and was never updated.
ID: 3292
Title: livestatus_status: Added Microcore relevant metrics like helper usage and latency
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.9i1
The livestatus_status check was missing some performance indicators like the helper usage
and check latency which are only available in the Microcore. These metrics have now been
added to this check.
ID: 3272
Title: oracle_tablespaces: severity of check for autoextension is now configurable
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.9i1
There is now a new check parameter that defines the check state in case that
the current autoextension setting does not match the expected setting. The
expected setting is either determined during discovery (default) or by an
explicit value in the rule.
By setting the state in such a case to OK the checking for autoextension
is effectlivey turned off.
Since the expected autoextension setting and the severity are two different
parameters you can easily create independent rules for the expected setting
and the severity of a mismatch.
ID: 3271
Title: New option in aggregation for tuning aggregation of downtimes
Component: BI
Level: 1
Class: New Feature
Version: 1.2.9i1
When computing the state 'in scheduled downtime' for an aggregate
first all leaf nodes that are within downtime are assumed CRIT and all others
OK. Then each aggregated node is assumed to be in downtime if the state
is CRIT under this assumption. You can change this to WARN now by checking
the new option {{Escalate downtimes based on aggregated WARN state}} in
the properties of an aggregation now. The influence of
this setting is especially relevant if you use aggregation functions of type <i>count</i>
and want the downtime information also escalated in case such a node would go into
WARN state.