Back to your phpLogCon instance
Here we are again with our rolling beta program
. The past has shown that its advantages to update a rolling beta, especially when features are added by request.
Rolling Beta means whenever we will add new features into MonitorWare Agent, this Rolling beta setup will be updated.
Registered users can use their current license with the rolling beta Versions. Feel free to test this new rolling beta version as we add partially features on demand. If you are experiencing any problems, kindly let us know via support email (support@adiscon.com) or this forum.
You can have a look into the Manual for MonitorWare Agent 3.0 Rolling Beta as well.
Download the current rolling beta from this link: http://www.adiscon.org/download/mwagentrb.exe
Below the change since version 2.1:
======================
2005-02-11 / build 271
======================
- Added New Services: A bunch of new Probe based Services have been added. This includes a FTP, HTTP, IMAP, NNTP, POP3 and SMTP Probe. All specialized on these protocols, and with advanced features and filter possibilities. More detailed information will follow soon in the manual.
- File Monitor: Fixed a bug in the File Name generation which caused the File Monitor not to process file changes anymore. For example when daily logfiles were monitored, and for one day no logfile was generated, the bug occurred and the File Monitor stopped working.
- SETP Sender & Server: Fixed a connection shutdown which only happened when a 4097 bytes large message was received.
- EventLog Monitor: Fixed minor bugs in the new SID Cache of the Eventlog Monitor.
- MWAgent Client: Recreated Filter Dialog and Insert Properties Content menus for better usability.
- MWAgent Client: Minor changes to make the Client overall more user-friendly.
- MWAgent Client: Fixed a error in the SNMP MibBrowser which only occurred for the first time it was opened.
======================
2005-01-25 / build 270
======================
- CPU Monitor: Total, Virtual and Physical Memory can now be configured separately.
- MWAgent Client: Changed the Popup Menu of the Services, RuleSet and Action menu. It looks now much better and is sorted by categories.
- MWAgent Client: Minor visual changes.
======================
2005-01-18 / build 269
======================
- SETP Action: Added two new Connection based configurable Timeouts, one is used during the connection and the other used when Receiving and Sending data. A higher timeout default might be useful in unreliable networks, or if the Server is under high workload.
- SETP Server: Fixed a minor bug that caused a "virtual" SSL Shutdown error.
======================
2005-01-07 / build 268
======================
- New Action HttpRequest added: This new Action can be used to simply request a webpage with a few parameters. This might be useful in order to trigger a web based application by the MWagent.
- Removed a minor Clientbug: If nothing was entered into the LastRecord value of the EventlogMonitor Eventoptions, the client crashed. This has been fixed now.
======================
2004-12-23 / build 267
======================
- SNMP Action & SNMP Receiver: Moved MIBPath configuration value to global options (See the General Options to configure). The reason is that we only can work with ONE SNMP Mib location store.
- SNMP Action & SNMP Receiver: If both were used, an access violation could have occurred while the service was stopped.
- SNMP Receiver: When a SNMPv2 message was received, the variable OID's were not fully resolved or included into the message. This has been fixed now.
- MWAgent Client: Added a MIBBrowser which can be used to browse through all MIBS that are installed with MWAgent. Custom MIBs are possible as well.
- MWAgent Client: For performance reasons, the MIBs are not loaded on startup, but at the first time they are needed (MIBBrowser). You can configure this behavior in the Client options.
======================
2004-12-15 / build 266
======================
- General Debug Logging: Enhanced the Debug logging format, you can now disable or enable all debug facilities individually. This makes the analysis of debug logs for you and for us much easier
======================
2004-12-09 / build 265
======================
- SETP Sender: Added a new Option "Session Timeout". Before this, it was a hard coded value but can be configured now. The default value is 30 seconds. That means a connection to the SETP Server will be at least kept open for 30 seconds. This reduced the connection overhead, specially for SSL based connections.
- SETP Receiver: Added a new Option "Session Timeout". Works as the Option in the Sender, the connection is kept open for at least 30 seconds (configurable).
- Database Action: Added a new option for the SystemEventProperties table has been added "Maximum value length". By default this option is set to 512, which is the default max length of the value field. If a property exceeds this length, it will be truncated automatically. This removes random occurring ODBC Error's when the property value was more then 512 characters.
- Fixed a bug in the Eventlog Action: If properties were used in the message, they got overwritten by the first occurrence of the action with fixed values.
- Connection handling in the SETP Server: Enhanced handling here, if problems occur during sending/receiving messages, more retries will be done.
- SEPT Sender: Fixed a minor bug in the connection close handling that has been introduced due the new "crash" handling in RB264
. This caused random EventID 114 error's in the Eventlog.
======================
2004-12-03 / build 264
======================
- Added new Action: Control NTService This Action can be used to control a service , you can Start,Stop, Restart, Pause or continue a Service.
- Added new Action: Compute Status Variable For more complex tasks, we have added a new action to increment or decrement a Status variable. Currently the "NTServiceMonitor Alerter & Recoverer" sample uses this action to implement a reminder.
- SETP Sender: Fixed a bug in the timeout function of the SETP Server. If the connection went down while the connection was kept open (for what reason ever), it could cause the Agent to crash.
- SETP Server:Fixed a bug in the decompression code (zlib) that could be caused by larger events and could cause the SETP Server to fail due memory corruption.
- NTServiceMonitor Alerter & Recoverer Sample: Recreated the sample, it now uses the Control NTService action and the Compute Status Variable action for the notification reminder. Also some problems have been fixed.
- MWAgent Client: Fixed a few bugs in the XML Import&Export functions. Some of the Global filter conditions were not correctly exported.
- MWAgent Client: Fixed a minor bug in the New Action Wizard. The Client crashed if you selected advanced and directly clicked Finish (without performing Step 2).
======================
2004-11-26 / build 263
======================
- SNMP Receiver: Fixed a bug if an Enterprise specific trap was received. The source was not correctly parsed, so the IP was not correctly shown.
- SETP Server: Compiled with the new OpenSSL library Version 0.9.7e (The dll's have also been updated).
- Property Engine: Added a new Property called "ntservname" which contains the internal Service name of a NT Service. The existing Service Name property has been renamed and still represents the "Service Display Name".
- EventLog Monitor: Fixed a bug in the new SIDCache feature, some SID's caused it to crash internally, which ended the EventLog Monitor Service internally, but not the MWAgent, itself.
- SETP Receiver: Fixed a bug that has been introduced to Build 261, caused the Agent to crash if messages other the from the EventLog Monitor were received over SETP.
======================
2004-11-23 / build 262
======================
- NTServiceMonitor Service: Added new Option "Generate an event if a Service is in the running state" which is needed for Alert and recovery handling of services.
- Start Program Action: Added new option to use the Property Engine in the parameters variable, which is needed for Alert and recovery handling. The old format is still useable if the legacy option is enabled.
- General: Added two new configuration samples into the setup, a PingProbe Alerter and a NTServiceMonitor Alerter & Recoverer. See the readme description for more.
======================
2004-11-22 / build 261
======================
- SETP Server: Fixed a memory leak in the SETP Server.
- General Bugfix: Fixed a few minor bugs where the debug output was not correct.
======================
2004-11-12 / build 260
======================
- File Monitor: Added support for UNICODE files. The detection of Unicode files is automatically and transparent for you
- Database Action: Fixed the handling of TEXT Type fields. Text fields can be build out of properties, so they are more customizeable then the other field types.
- Client: Fixed minor bugs in the FirstTime Wizard and in the Defaults of the new DB Action
======================
2004-11-10 / build 259
======================
- File Monitor: Added new feature, you are now able to customize the line delimiter. For example you can split by two line feeds (would be configured with \r\n\r\n).
- File Monitor: Increased the line buffer the File Monitor can hold up to 64KB. It can also be configured now, but values above 64K will not be used at the moment.
- Status Filter & Action: Fixed a bug introduced on one of the prior Rolling Beta versions which caused the Status Filter & Action not to work correctly.
======================
2004-11-08 / build 258
======================
- Syslog Server: Added new feature for Syslog over TCP. You can now configure a message separator. This separator will be used to split Syslog messages which is useful if your Syslog sender is sending lots of Syslog message in one TCP Session.
- Syslog Server: Added two Timeouts for Syslog over TCP. Message receive Timeout and Session Timeout. Once the Syslog Server starts receiving a message, it will it will wait until it receives a message separator (if configured), or until the Message completion timeout occurs. The session timeout is an additional timeout.
- SETP Server: Added startup retry handling into the SETP Server, it now does,as the other TCP based Services, retry to bind the Sockets during startup.
- SETP Server: Fixed a bug in the Shutdown procedure of the SETP Server which could occur if SSL was enabled and the MWAgent Service was stopped.
======================
2004-10-27 / build 256
======================
- SendSETP Action Bugfix: A problem could cause a hang/lag in the processing of MWAgent if the SETP Send Action was used. The reason was wrong handling of the connection shutdown.
- Debug enhancement: The debug format has been highly enhanced. Each debug line now is prepended by some general parameters. ThreadID, Unix TimeStamp and the Debuglevel. This will make the debug file much more readable and easier for analysis.
======================
2004-10-22 / build 255
======================
- SNMP Action: Corrected OID Variable Handling. OID's are now correctly loaded. If they can not be resolved (for example due typo reasons), they won't be send.
- SNMP Action: The Value of a Variable is now expandable with the property engine.
======================
2004-10-21 / build 254
======================
- Several Performance Optimizations: Most of them were done in the EventLog Monitor.
- Idle Priority: Added Idle in the ProcessPriority selection.
- Added SID Cache: Added a cache for SID's which are primary resolved in the Eventlog Monitor. This improves the performance when reading the Security log for example.
- New EventLog Corruption Handling: Introduced new Eventlog Corruption handling which is also available in MWAgent 2.2
======================
2004-10-01 / build 253
======================
- SNMP Action: Added support for additional SNMP variables. You can now add them dynamically, different types can be chosen but haven't been tested yet.
- SETP Send Action: Added support to compress data. WARNING, this feature will require at least MWAgent 3.0 RB253 as SETP Server on the other side, otherwise the send will not work. Due our first tests, we reached compressions of 30-50% with usual eventlog messages.
- SETP Server: Added support to decompress data. Please note that uncompressed SETP Messages can still be received. This feature works more very transparent on the server side level.
- Client Bug fix: The new Client did not correctly import the enabled state of the Eventlog Monitor configurations. This has been corrected now.
- Known Bug: There is a known bug when you shutdown MWAgent which is using SETP Send Action. This will be fixed within the next release. Currently, you just have to wait approx. one minute until the MWAgent shuts down forcefully.
======================
2004-09-22 / build 252
======================
- Property Engine : Minor bug fix which could cause error's during shutdown of the MWAgent.
- EventLog Monitor : Major enhancement in the EventlogMonitor. It is now possible to process eventlogs from custom Eventlogtypes. You can configure as many custom Eventlogtypes as you want in a configuration list.
======================
2004-09-16 / build 251
======================
- Changed RB to 3.0 Version : Due the amount of new features(and those who will come), we decided to move to the 3.0 Version. There will still be a 2.2, with many of the features which have been added during this thread, but not all. This Version of MonitorWare Agent will also still run with your 2.x license (till April 2005).
- Protect Agent against Service shutdown: This new feature has been added. When enabled, the Agent will not stop processing the internal queue when it is stopped. Please note that it will remain in the stopping state then.
- First Time Wizard: A new Wizard has been added which only occurs the first time when you start the MWAgent Client. This Wizard will help you configuring MWAgent for general common tasks. For existing users, just Cancel the Wizard, it won't come up again.
- Bug fix - NTServiceName Filter: A side effect of the Rb238 Filter bug fix caused a problem with this filter. This has been fixed now.
======================
2004-09-10 / build 239
======================
- Discard Action: Some internal changed introduced to Build 238 caused the Discard Action to crash if it were used. This has been fixed now.
======================
2004-09-09 / build 238
======================
- Filter Engine: Fixed a bug with the Event Type filter, it was ignored.
- Property Engine: Fixed a bug that the %NTEventLogType% property could not be found.
- SendSyslog Action: If the message format was customized, the message was completely altered and not temporary. This has been fixed now.
- Eventlog Monitor: Added two new advanced Options.
1. Do NOT process existing entries when Eventlog corruption occurs (Event 1011 related)
2. Do NOT process existing entries on Service Startup
======================
2004-09-07 / build 237
======================
- Database Action: Highly optimized the new database action, it's a lot faster now.
- Database Action: Removed a bug which caused slow performance under stress circumstances.
- MonitorWare Echo Request Service: Removed a bug which caused problems when requesting multiple MonitorWare Echo Reply Services.
- General Registry Changes: From now MWAgent will handle line feeds different as you can't import them by regedit.exe. The change is completely transparent to all functions.
- General Bugfix: Removed a memory leak that was caused by disabled actions.
- General Bugfix: In some cases the system doesn't free a socket fast enough (for example when you restart the service). An handler for this has been added which retries starting Services like the Syslog or SNMP at least for one minute long.
- SNMP Receiver: Corrected error handling for specific cases.
======================
2004-08-13 / build 236
======================
- CPU Monitor: Fixed a bug that could occurred if multiple CPU Monitor services were used (All after the first did not start)
- General Bug fix: Fixed a bug that could cause a leak of TCP Connections under stress circumstances (for example having more then 5000 failed connections per minute).
- SNMP Receiver: Replaced the UCP-SNMP with the new NET-SNMP library.
- New Action: Send SNMPTrap: This action currently supports sending of V1 and V2c SNMPTraps. Additional OID variables are currently not supported, but this will be soon.
- SNMP Receiver & Sender: Enabled MIB parsing support. MIBs can now be loaded and are located in the MIBs directory by default.
- MonitorWare Echo Reply Service: Had an error that prevented successful service start. This has been fixed.
Important The SNMP functionality has undergone some fundamental changes. This was necessary for MIB parsing as well as planned further enhancements. The current code in the rolling beta is weak - we expect that it takes at least until end of August/mid of September until this is mature again. We appreciate any feedback you have on the new SNMP functionality. But please be warned that you might experience quite some trouble with SNMP.
A note for update installations, unfortunately the installer is not capable to install the new MIBS files during an update installation.
To workaround this problem, right after update start the installation again. Then select Modify and click on next. After this step, you can expand The MonitorWare Service feature and enable the SNMP Mibs feature.Then click on next to change the installation, and the new Mibs files will be copied into your installation folder.
Alternative you can download and extract the Mibs files from here: http://www.adiscon.org/download/mibs-mwagent2.2.zip
======================
2004-08-02 / build 234
======================
- Eventlog Action: Event Source is now fully configureable
- Eventlog Monitor: Added support for SID Resolving (can be enabled/disabled per Eventlog)
- SMTP Action: Fixed a bug which could cause multiple socket error's if the mailserver disconnected during transmission.
- Debugging: Added more debug support into the debug logfile
- MonitorWare Agent Client: Added more common functions (like using CTRL + S everywhere) and made it more userfriendly.
- MonitorWare Agent Client: Copy and paste works on many positions now
======================
2004-07-21 / build 233
======================
- Database Monitor: Added more handling for different ID Column value types, specially if the ID Column is a number type field. This was also tested against Oracle databases ( samples tables ).
- MonitorWare Agent Client: Filter Editor: Enhanced the filter editor with a few new features. This includes copy&paste, add comments per filter and minor others. The copy&Paste feature works also between different rules and filter sets.
- MonitorWare Agent Client: Handling Actions: Actions are also copy&paste able now. You can copy&paste them between rules and even rulesets if you want.
- MonitorWare Agent Client: Expanded in Treeview: Is now saved. That means the Client will open exactly like you left it last time.
======================
2004-07-02 / build 232
======================
- Added new Services: MonitorWare Echo Reply and Request Services: These two services together can be used to check in real-time if MonitorWare Agents are alive. The Echo Reply service is used on each of the installed agents. Then, a central agent is using the Echo Request and instructed to poll each of the other Agents. When the Request can not be carried out successfully, an alert can be generated. The MonitorWare echo protocol ensures that always a fresh probe of the remote agent is done.
- Bug fix: when an empty Syslog tag value was configured in any service, garbage could be used instead. This has been corrected.
- Event Log Monitor: added an option to allow ignoring existing events on service startup. This is now an optional item which can be configured via the advanced options dialog (on a per-log basis).
- Event Log Monitor: added an option NOT to remove control characters and compress spaces in the event log monitor. This is useful for emailing events as well as in DBCS environments (e.g. in Japan).
- added additional reliability checks to the service so that an invalid configuration is handled better
- Client changes: Introduced a few usability and stability changes like:
Use CTRL + S to save your settings
Move Rules & Actions up and down by using Toolbar buttons (Fast then the context menu)
Highlighting of the current selected entry in the Tree view
Reorder of the Rule & RuleSet menu.
Other minor changes
======================
2004-06-25 / build 230
======================
- Database Monitor: Moved some options into a new Advanced view and added a new option to define the message format. There are three Options to what the message can be configured now:
NONE = The %msg% will not be filled with any data, it will just be empty.
CSV (comma-separated values) = One data record will be represented by the common CSV format. Fields will be separated by comma (,) and strings will be quoted. Quotes within strings will be double quoted automatically.
Custom = Selected by default and filled with this text: "Actual values are in XML stream - see http://www.monitorware.com/Common/en/FA ... values.php for more information." Within this field, you can create custom formats like in many other actions.
- Database Monitor: Important change of the properties that are generated by the Database Monitor. All fields are automatically set as property prefixed with "db-". That means a field called "ID" would be represented as "db-ID" property in the property list.
- Added new Service: CPU Monitor - This Services allows you to monitor CPU and Memory usage of your local computer. Documentation regarding this new Service will follow soon.
Additional Information for NT4 Users. You may need to install WMI for NT4 in order to use this new service: WMI CORE 1.5
======================
2004-06-16 / build 227
======================
- Added more error handling into the new DB Action. It now detects if a table or field is missing and reports it correctly as error into the application Eventlog.
======================
2004-06-15 / build 226
======================
- Reopened the Rolling beta program
- Rewritten the complete ODBC Database Action. It is much more flexible and configurable. You can dynamically add and remove fields you want to update in your Database Action.
