Information: Forum is in read-only mode
For details and other support options see https://www.adiscon.com/news/support-forum-set-to-read-only-mode/

MWAgent 8.0 Build 408RB - Updated 2011-04-21

Support, Questions and Discussions on MonitorWare Agent

Moderator: alorbach

Google Ads


MWAgent 8.0 Build 408RB - Updated 2011-04-21

Postby alorbach » Wed Dec 15, 2010 5:06 pm

Hi,

The Rolling Beta program is again open, features and bugfixes will be added continuously. The changelog below helps you to keep track on the changes.
Feel free to test this new rolling beta version, if you are experiencing any problems, kindly let us know via support email (support@adiscon.com) or this forum.

A note on Win32 and x64 Edition
The MonitorWare Agent Service component is shipped as win32 and x64 build, and automatically installed depending on what Windows Version you are using.

:arrow: Download of the rolling beta
:arrow: MonitorWare Agent 8.0 Rolling Beta Manual

Below the change since version 7.2:

:!: 2011-04-21 / build 408
- Enhanced SSL Security in Syslog / SETP service and Actions.


:!: 2011-04-18 / build 407
:arrow: Features
- Added error handling in EventLog Monitor V2 for new EventLog Polling method in case the last record is wrong. The last record will be set to the last eventlog record in this case.
- Added IPv6 support for Relp Service and Action. Usage of IPv6 is automatically done by the RELP library during runtime if installed and available.
- Upgraded NET-SNMP to library Version 5.6.1.
- Added support for IPv4/IPv6 and TCP/UDP in SNMPTrap Monitor, SNMPTrap Receiver and in SendSNMP Action. All these Services/Actions can now use a combination of UDP/TCP and IPv4/IPv6.

:arrow: Bugfixes
- Also hardened SNMP Trap Monitor and Receiver against invalid SNMP data.


:!: 2011-04-08 / build 406
:arrow: Features
- Added support for polling EventLog Records in EventLog Monitor V2. This works almost like the old EventLog Monitor, the Eventlog channel is polled frequently and new EventLog records are processed only. By default, the "Subscription Model" is used which processed events in realtime.
- Added support to read and process EVTX files. This requires the new "Eventlog Polling" method in EventLog Monitor V2. It is also possible to update the the EVTX files while MonitorWare Agent is running.


:!: 2011-04-05 / build 405
:arrow: Features
- Added Option to Force UTF8 Decoding in Syslog Service. Now there is an Encoding configuration tab which lets you decide if you which to automatically detect the encoding, force UTF8 decoding, or use system default encoding.


:!: 2011-04-01 / build 404
:arrow: Bugfixes
- If RawXML Format is used in messageFormat (EventLog Monitor V2), we now include the Eventlog Message in the <RenderingInfo> Node if the message can be properly compiled.
- Hardened SSL transmission send or receive handling. This affects all Services/Actions which use SSL.
- Hardened SSL initialization which could cause startup problems if multiple services with SSL were configured.
- Corrected SSL Error logging in on connection shutdown.
- Fixed a bug causing a crash on startup if a configured Syslog Port was blocked by another application.
- Added option to add ProcID into SyslogTag for RFC 5424 Header parsing. This was previously default. The Option is disabled by default now making it easier to filter for the SyslogTag.
- Added Performance fix for UTF conversion for empty strings.


:!: 2011-02-17 / build 403
:arrow: Features
- MonitorWare SETP Protocol extended to V3. If both Sender and Server have V3 or higher, we use UTF8 encoded messages. This maintains the correct character encoding after the messages is received and rebuild internally.
- Implemented OutputEncoding option ODBC / OLEDB Action for 8 Bit (var)char fields. This supports writing UTF8 encoded messages using MySQL ODSBC 5.1 Driver for example.
:arrow: Bugfixes
- Fixed issue in Datestring creation of the Emailheader (Send Email Action). The first digit pair of the time was not correctly build with two digits as per RFC2822. Restrict Mailclients could not handle this.
- Fixed UTF8 Encoding detection for Syslog RFC 5254 formatted messages. This includes the BOM starting before the Syslog message, and not the Syslog Header.


:!: 2011-02-04 / build 402
:arrow: Features
- Added initial support for IPv6 in almost all network relared Services and Actions. This is a major step forward in the evolution of the MonitorWare Agent product. All client related network actions will automatically detect IPv6 and IPv4 target addresses. You can also use dns resolution to resolve valid IPv6 addresses. For network related listener services, you can configure IPv4 or IPv6 as protocol. A service can either run as IPv4 or IPv6 based service. In order to support both protocols, you will need to create two services. Currently, RELP and SNMP related services and actions do not support IPv6 yet. This will happen in near future.
- Added support for EHLO in SMTP Listener Service.


:!: 2010-12-15 / build 401
:arrow: Features
- Added new Action called Send MSQueue. This action can send messages to a Microsoft Message Queuing Server. Currently it is possible to customize the Queue Label, Priority and Queue Body. The Queue Body contains the message property by default as UNICODE (UTF16) string. In order to use this action, you need to have the Microsoft Message Queuing (MSMQ) Server installed.
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Google Ads


Return to MonitorWare Agent

Who is online

Users browsing this forum: No registered users and 0 guests

cron