We continue to charge ahead with behind the scenes enhancements but have found the time to bring you some much anticipated features and improvements. The May release (v42) will be rolled to customers during the second half of the month.
- NetApp SnapMirrors can be monitored by using the NetApp API. When adding a datasource for a NetApp collector, selecting API call as the collect method, snapmirror-get-status as the API field, and snapmirror-status as the Index Property will enable monitoring. Parameters and datapoints must be added.
- A new report type, Interface Bandwidth, provides visibility to average and maximum inbound and outbound traffic.
- Services alerts can be configured based on multiple testing locations, enabling alerts to be refined based on all, half, or one testing location. Status graphing is available for all testing locations combined as well as each individual location.
- Date / Time data in Alert Reports is in the format yyyy-mm-dd hh:mm:ss to enable international date formatting.
- Web Service Overview reports will display changes in status, treating status changes as events rather than performance data.
- When creating an Alert report, the option "Include pre-existing alerts?" will include all alerts that meet the report parameters independent of the last activity date. For example, an active alert report for the past day will only include alerts created and active with the last 24 hours. Selecting 'Include pre-existing alerts?' will display any alert that has had a status of active in the last 24 hours.
- Simplified process to add Windows Services, Windows Processes, and Linux Processes as monitored resources, providing a real time list of processes to select from. To add, right click on the host name, select More | Add Monitored Resource.
- New active discovery filter, packetsRX, supported for the ESX Host Interface datasource
- When creating or editing Log File EventSource, users were prompted for Alert Severity. The severity is handled within the Log File Collector Attributes so the Alert Severity configuration has been removed.
- The Alert History table has a new column for 'Acked On.'
- Graph images are generated server side as pngs, improving processing times.
- Various graphing updates, including an increased margin for the Y axis to accomodate large values, text wrapping in legends, and tool tips displaying datapoint descriptions consistently
- The drop down list for available groups when adding a filter in the Alert Tab has been reactivated.
- Collectors were rejecting a feed if a filter had been created by API that did not have a value, or a host without a hostname. With this release, missing values will not cause an exception.
- Scheduled Down Time for event sources and data sources will be reflected in the Host | Managed Scheduled Down Time | SDTs affecting this object window.
- Invalid date formats no longer cause issues for collectors when processing syslog messages
- The Host group inventory group reports would include sub groups regardless of the include subgroups setting
- Fixed situations in which ##ALERTTYPE##, ##COLLECTORDESC## and ##COLLECTORID## tokens were not rendered correctly.
- Disabling a datasource at the group level was not updating child groups.
- The escalation level of an alert was being passed through when time based subchains were in use, causing a newly triggered chain to begin with an escalation point. Time based subchains will now always start at the first stage.
- The application was not correctly displaying event source status in regards to Scheduled Down Time.
- Corrected various links to help documentation throughout site
- When an EventSource Log File Collector Attribute matched a trigger and a not trigger parameter the alert was sent. Alerts will only be sent if the trigger matches and the do not trigger does not match.
- Host Cluster alerts were applying the thresholds of the specific hosts in place of the Host Cluster alert thresholds and the Host Custer Alert email was not being sent.
- Ability for Readonly/ackonly roles to add hostgroups has been removed.
- When a new user was created and "Force Password Change" selected, the user was not prompted to change the password at next login.
- The application was not correctly displaying an acknowledged collector down alert
- Scheduled Down Time for hosts and instance groups could not be edited if the SDT review window was opened from right clicking Group Name and selecting Show hosts with scheduled down time.
- Adding arbitrary emails to a stage in an escalation chain required commas to separate multiple addresses
- MsSql JDBC Active Discovery was not working as expected