Table of contents[Index] FineConnection web site[FineConnection web site]

Version FP1.85.333-Beta1

This new version is primarily a maintenance release focusing on reliability and speed. It will not add many new features and options because most of the (many) changes are "under the hood".

  1. In previous versions Monitor one used the Borland database engine (BDE) for storing project data. In this version, the BDE has been replaced by the Firebird SQL database for stability and performance reasons. Firebird is a relational database offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. It has been used in production systems, under a variety of names since 1981.
  2. New 1 and 10 minutes polling queues for supporting SNMP agents that update their counters on a 1-minute basis. The 10 minutes queue is only available for History Shooters.
  3. Improved MIB compiler. SNMPv2 is now fully supported (including SNMPv2 traps).
  4. Many bug fixes and improvements from which the most important one: a severe memory leak in one of the background threads that take care of saving data to the database!
  5. The Monitor one implementation of Trap filtering has almost completely rewritten in order to facilitate SNMPv2 filtering. Receiving and filtering of SNMPv2 traps is now fully supported. Blocking and unblocking of traps by adding or removing filter rules is now simpler than ever.
  6. In previous Monitor one versions, for History Shooters, a new "data-collection" session was created each time Monitor one was started/restarted. In this new version, the "old" session is simply restarted and newly collected History data is appended to the already existing data. This scenario is much more user friendly. It prevents you from getting lost in too many (usually almost empty) sessions and provides better trending functionality.
  7. Two new default menu-items have been added to a device’s right-click menu: The Desktop menu-item (which starts MSTSC.exe /v:<IPaddress>) and the History menu-item. The History item is only enabled if there’s at least one History Shooter running for the device. The History menu-item provides quick access to logged history data.
  8. In previous Monitor one versions, Trap, Syslog and Sensitivity (TSS) events were displayed on a separate tab on the "Event control" window. In this new version, this tab no longer exists and the TSS events appear on the Pending events list (along with the "No response" and "Threshold exceeded" events). However TSS events are treated differently compared to "No response" and "Threshold exceeded" events. TSS events differ from "No response" and "Threshold exceeded" events in the sense that they do not have a start- and end timestamp. They are "one-shot events" that cannot get the status "pending". "No response" and "Threshold exceeded" events are kept in the list until the problem is solved. They can be acknowledged but not removed. TSS events are kept in the for xx seconds or until acknowledged or removed! You can adjust the preferred behavior on the Alerting tab of the Globl configuration window.
  9. A variation on the already existing IDFFS ("Is Different From First Sample") operator is the new HCF ("Has Changed From") operator for threshold monitoring. The HCF operator compares retrieved values with the specified threshold value and generates a "Threshold exceeded event" when the value changes from the threshold value to another value. The HCF operator is ideal for health monitoring! It can help you detecting if the temperature in the computer room changes from the adjusted value, if there are hardware problems on servers (fan, disk etc) or if a port on a switch gets the "down" status while it is normally up!
  10. A device’s Serial# and Registration# can now also be included in the body text of an alert email.