03.03.2015 Views

MonitorMagic - Tools4Ever.com

MonitorMagic - Tools4Ever.com

MonitorMagic - Tools4Ever.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Release notes<br />

See also:<br />

Features <strong>MonitorMagic</strong> version 3.0<br />

Fixes <strong>MonitorMagic</strong> version 2.0<br />

<strong>MonitorMagic</strong> version 2<br />

Features <strong>MonitorMagic</strong> version 2.0<br />

Version 2.0 build (1074), February 8, 2002<br />

Support SNMP traps. See SNMP traps for more information (1073, 1/31/2002).<br />

Support sending pager - SMS messages using a modem (1073, 1/31/2002)<br />

Dragging a policy directly to a open Monitor Window is now supported; (1060)<br />

In the web interface, in you can now view <strong>MonitorMagic</strong> rules and acknowledge them<br />

when triggered.(1060)<br />

The possibility to terminate processes through the web interface is added. (1060)<br />

Implemented the option to enable anonymous access to the web interface. The option to<br />

use the Service account has been removed.(1060).<br />

Added several pre-configured example policies. (1065)<br />

Version 2.0 build (1050)<br />

<strong>MonitorMagic</strong> version 2.0 supports the <strong>MonitorMagic</strong> Web interface. See the<br />

<strong>MonitorMagic</strong> Web Interface for more information.<br />

Supports monitoring process.<br />

Supports the alarm action to terminate a process on a local or remote <strong>com</strong>puter.<br />

Supports the alarm action to reboot or shutdown a <strong>com</strong>puter.<br />

Fixes <strong>MonitorMagic</strong> version 2.0<br />

Version 2.0 build (1074), February 8, 2002<br />

Web interface: A problem to acknowledge rules has been fixed.<br />

Web interface: Performance counter icons are now displayed correctly.<br />

When creating a monitor on processes, the "add" button is now correctly enabled when<br />

specifying the the name of the monitored process manually instead of from the list of<br />

running processes. (1060)<br />

When connecting with SSL to the browser, and entering an incorrect password, the<br />

notification to the user was unclear(1060).<br />

An alarm action could be configured to fire when a rule is "no longer triggered". The<br />

alarm action was however not actually fired. Now it correctly is. (1060)<br />

An alarm action could be specified to fire when "rule triggered and not acknowledged<br />

within ... minutes". This wait time was incorrectly calculated relative to the time that the<br />

rule criteria where exceeded, and not relative to the time that the rule was triggered. (a<br />

rule can be specified to trigger only after the criteria are exceeded for a specified amount<br />

of time). Now the time the program waits for the acknowledgment is relative to the time at<br />

which the rule triggered.(1060)<br />

Slightly modified the position of some buttons in window for editing monitors to prevent<br />

accidentally pressing the cancel button. (1060)<br />

When renaming alarm actions directly in a active monitor, the alarm action was<br />

duplicated instead of renamed. Now it correctly renames.(1060)<br />

When a monitor was created on a specific server, e.g. by applying a policy, the monitor<br />

was always executed once on creation. For monitors that should execute at a fixed time<br />

this does not happen anymore(1060).<br />

17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!