ID: 2828
Title: win_disks: now able to handle disks with missing size or media type information
Component: HW/SW-Inventory
Level: 1
Class: Bug Fix
Version: 1.2.7i4
ID: 2902
Title: Hosts can now be added by regular network scans of configured IP ranges
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
For each WATO folder a new attribute <i>Network Scan</i> can now be configured.
This network scan will ping all IP addresses in all configured IP ranges in the
configured interval for new reachable hosts / IP addresses.
When such a network scan of a folder discovers a new host, the discovery mechanism
tries to resolve the host name via DNS. If found, it uses the DNS name as hostname.
Otherwise the IP address will be used as host name. Then it will be created as new
host and added to this folder.
Hosts found by the network scan are added as disabled host. You can enable monitoring
of these hosts by setting the <i>Criticality</i> host tag of this host to another
value. Additionally you may want to configure other attributes like the agent type
of this host before adding it to your regular monitoring.
If you want to exclude a found host from your monitoring, add the IP address to the
list of excluded IP addresses and then delete the found host from this folder.
The result of a network scan is written to the <i>Last Scan Result<i> attribute
of a folder. So if you like to know when the last scan for a folder was performed,
take a look at that folders properties.
If you experience issues with the network scan, take a look at the log of the Web GUI
(<tt>var/log/web.log</tt>).
ID: 2826
Title: Disabled BI Aggregations no longer causing crashes when using "Precompile aggregations on demand"
Component: BI
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This fixes the error <i>AttributeError: class DISABLED has no attribute 'lower'</i>, which is shown in
the BI sidebar snapin or written to the file <i>~/var/log/web.log</i>.
Because of this bug most of the aggregation views were empty.
ID: 2921
Title: printer_supply_ricoh: check now tries to handle negative readings properly
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
Negative values are used by the device to report "special" conditions. Unfortunately these aren't
documented so current interpretation is only based on observation.
ID: 1322
Title: solaris_prtdiag: New Check for Solaris Hardware State based on prtdiag
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2920
Title: hr_cpu: this check can now also display per-core graphs
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
per-core graphs are optional and have to be enabled through the rule "CPU utilization for simple
devices"
ID: 2919
Title: hp_webmgmt_status: New check for health status of various Hewlett-Packard devices
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
This check supports different device types but apparently not all models. Among the supported devices are some
switches and tape libraries of the storever series.
ID: 2924
Title: WATO can now add contact groups from hosts also to services
Component: WATO
Level: 1
Class: New Feature
Version: 1.2.7i4
In WATO in a host or folder you can assign contact groups to hosts.
The new checkbox <i>Always add host contact groups also to its services</i>
allows you now to also assign these groups to the services of the host.
Here is some explanation from the online help:
<i>With this option contact groups that are added to hosts are always being
added to services, as well. This only makes a difference if you have assigned
other contact groups to services via rules in Host & Service Parameters. As
long as you do not have any such rule a service always inherits all contact
groups from its host.</i>
ID: 2923
Title: SNMP community in WATO is now always displayed with ******
Component: WATO
Level: 1
Class: New Feature
Version: 1.2.7i4
This is due to security. SNMP communities are basically passwords and should
not be shown in plaintext in the GUI. Of course this change makes it harder
to read existing rules. If that is a problem for you then you can add the
plaintext community to the comment field of a rule. Alas - security is always
linked with inconveniance...