ID: 0621
Title: zfsget: better filesystem selection and calculation of sizes
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i4
zfsget now only inventorizes filesystems of type "filesystem".
If a mountpoint is present several times in the zfsget section of the agent
data (with different device name), and also in the df section, the entry
in the zfsget section with the device name from the df section is taken for
calculating the data.
ID: 0620
Title: new version of Check_MKs hardware and software inventory including a much extended windows agent and inventory functions
Component: HW/SW-Inventory
Level: 2
Class: New Feature
Version: 1.2.5i4
ID: 0935
Title: CPU utilization: increased maximum value to 10000
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i4
The maximum value for the CPU utilization in the WATO rules "State and count of processes"
and "Process inventory" was set to 101 percent. There were some instances where this value was higher than this limit.
For example if an application used multiple CPUs or the utilization value was calculated for a group of processes.
ID: 0166
Title: mobile gui: Fixed colors of command list
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.5i4
The link color is now black instead of white. This is much more readable.
ID: 0619
Title: adva_fsp_temp: new check to monitor temperature and temperature trends on ADVA scalable optical transport solutions
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i4
ID: 0816
Title: States of events can now be set by patterns
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.5i4
The states of events created by a rule can now be set by regex patterns. A rule can now
create events with different states. The mechanism is as follows:
1. The "text to match" patterns needs to match a message
2. When a rule has configured "(set by message text)" as state, and patterns are defined
for the single states, the message will be matches agains these patterns to calculate
the state of the event.
3. When none of these patterns matches, the event is set to UNKNOWN