LogMeister > Version History
Version History
LogMeister
This shows you how often LogMeister was updated with us over the past few months. Whenever available, we also include additional information for each update (new features, changes etc.).
version 3.0.6.0 - posted on Nov 11, 2009
- No further details available
version 3.0.4 - posted on Jul 20, 2009
- No further details available
version 3.0.3.0 - posted on Jul 03, 2009
- No further details available
version 3.0.1 - posted on Apr 30, 2008
- Added option to Text Log Wizard to deal with logs that are rewritten periodically to limit their size. This can be set on existing feeds by right-clicking on the feed and choosing `Wizard...` from the resulting popup menu.
Raised cap on notification sensitivity from 10 to 70
Updated installer (some improvements for Vista)
version 3.0.2.0 - posted on Mar 18, 2008
- No further details available
version 3.0 - posted on Jan 15, 2008
- Custom reports / Custom Outputting and Archiving Formats
Option to Run script, batch file or executable when scheduled report or data archive is generated.
Bulk event feed creation from an external file
New XML Feed Type
Text logs - option for close to real time updates as well as regular polls
Action notifications improved - now has Run As... to launch command under specific account
Field substitution in action notifications
Improved aggregate definition user interface
Hierarchical display and navigation of feed groupings
version 2.6.3 - posted on Oct 11, 2007
- Fix: text log parser no longer breaks very long lines when reading unicode files
version 2.6.2 - posted on Apr 24, 2007
- Added ability to change the text that is used to assign icons to event
types.
Improved compatibility with hardware DEP on Vista.
version 2.6.1 - posted on Feb 21, 2007
- - Changes to ensure correct icon used for German event log entries. - Compatibility fix for certain CA products.
version 2.6 - posted on Dec 02, 2006
- - Vista compatibility. Please see the Troubleshooting section in the help for additional configuration steps if you are attempting to retrieve event log data from a remote Vista PC (i.e. a PC other othan the one running LogMeister).
`Catch events as they arrive` is now the default event log retrieval method. In most cases it has the least cpu and network load.
Added new filter rule, allowing construction of notifications and filters that require a date/time to be within the last X hours or days.
version 2.5.5 - posted on Sep 20, 2006
- NOTE: This release changes the format of the Notifications.dat file. We recommend that existing users take a backup of that file prior to upgrading. For more information on taking backups, please see the Help.
Notifications can now fire when new items have not been seen within a certain time period, e.g. if a service indicates a healthy state by issuing regular information events, you can now be alerted when such events have ceased to appear.
Fix: Prevented rapid-fire poll failure notfications for event log feeds using `catch events as they arrive` method
Changes to help ensure correct app/svc synchronization at registration time
version 2.5.1 - posted on Aug 23, 2006
- - Added ability to insert placeholders for feed name, computer name etc. directly into the subject line of emailed notifications. The placeholders are replaced with the appropriate value when the email is sent.
version 2.4.1 - posted on May 02, 2006
- Fix: Changes to ensure that the service s copy of the aggregate feed definition is always up-to-date.
version 2.4 - posted on Apr 13, 2006
- Major changes to make filtering and notification rules more powerful and flexible
Improvements made to reduce memory usage when handling logs that receive new items very frequently
version 2.3.5 - posted on Feb 14, 2006
- Improved date store file handling
Improved interface for aggregate feed creation. It s now possible to select multiple feeds to populate the aggregate definition more quickly.
Assorted UI improvements
version 2.3 - posted on Nov 01, 2005
- Added facility for quickly copying settings from one feed to many others
Now preserves German `umlaut` and other language-specific characters
version 2.2.0.0 - posted on Sep 22, 2005
- Added automated report generation for feeds. This is available only for licensed copies of the application. As this release changes the format of feed definitions, we recommend backing up your existing feeds prior to installing this update. Please see the section titled `Backing up and Transferring Settings` in the Help for more details.
Improved automated feed compaction
Improved scrolling behavior in filter dialogs
version 2.1.7.0 - posted on Aug 03, 2005
- Improved text parsing efficiency
Improved handling of certain irregular text logs
Tray icon now automatically re-instates itself if Explorer is restarted.
version 2.1.6.0 - posted on May 29, 2005
- Added the ability to re-edit existing text feeds and change column definitions
Added support for non-standard characters in Event log connection passwords
Improved validation for regular expressions.
version 2.1.5.0 - posted on May 02, 2005
- Added new dialog for viewing all fields of a single item, similar to Event Viewer s properties dialog.
Added presentation of login credentials for notifications that write
to network shares/drives
Added the ability to store the data folder in custom location
see
section of the Help titled `Backing Up & Transferring Settings` for details
Improved handling of damaged data stores
Reduced cpu utilization in front-end app for `catch events as they arrive` feeds
version 2.1.0.0 - posted on Mar 31, 2005
- User-defined grouping of feeds, with group enable/disable.
Logs produced by notifications can be emailed automatically according to user-defined schedule. XML logs can be converted to HTML report format if required.
XML type added for logs produced by notifications
Duplicate facility for Notifications
Full control over the text in email notifications (better for those using an email-to-SMS service)
Ability to easily transfer view settings (column selection, width ordering and filtering) to multiple compatible feeds.
Ability to view current settings for Windows Firewall and enable the
firewall and logging from within LogMeister
LogMeister now retrieves the additional column in the Windows Firewall logs that shows transmissions from local applications that have been blocked.
Improvements to handling of illegal characters in text logs
File spec for text logs can now be edited from feed properties
version 2.0.1.1 - posted on Mar 07, 2005
- Fixed non-scrolling event log selection tree.
List control displaying available computers now holds its current scroll position during network enumeration
version 2.0.1.0 - posted on Feb 17, 2005
- Installer now accepts domain accounts, as long as they re members of the local Administrators group.
If the front-end application is launched under a different account from the service, a warning message will be displayed.
Event Log Feed wizard now allows multiple feeds to be created in a single pass.
WMI connection settings adjusted to improve compatiblity with domains containing XP/2003 computers.
version 2.0.0.0 - posted on Jan 25, 2005
- Option to run as a service
Support for Unicode characters in text Logs
Configuration options for optimisting LogMeister for various server conditions (Previously optimised for servers with small to medium sized Event logs)
version 1.1.0.4 - posted on Dec 09, 2004
- Fix to ensure that icons are retained when installation is moved to different PC or a different account on the same PC
Adaptive timeout in Event Log Wizard when determining available logs
Added minimize to / restore from tray animation
version 1.1.0.3 - posted on Oct 20, 2004
- Self-tuning timeout used to prevent intermittent poll failure on slow PCs/large event logs.
Status bar feedback improved.
Installer includes latest version of gdiplus.dll from Microsoft to counter jpeg vulnerability (Microsoft Security Bulletin MS04-028)
version 1.1.0.2 - posted on Aug 24, 2004
- No further details available
version 1.1.0.1 - posted on Aug 12, 2004
- This updates the initial release to correct a bug that can occur on the very first run of LogMeister. Under certain circumstances the bug caused LogMeister to be unable to detect event logs on local/remote computers during the first run, and did not recur once LogMeister had been quit and restarted
