Month: June 2014

2014-06-13 MonitorWare Agent 9.3 released

Adiscon is proud to announce the 9.3 release of MonitorWare Agent.

This is the maintenance release and contains mainly bugfixes.

Most notably, this version includes OpenSSL library 1.0.1h. This fixes all security issues from the OpenSSL Security Advisory (2014-06-05).

Detailed information can be found in the version history.

Version 9.3 is a free download. Customers with existing 8.x keys can contact our Sales department for upgrade prices. If you have a valid Upgrade Insurance ID, you can request a free new key by sending your Upgrade Insurance ID to sales@adiscon.com. Please note that the download enables the free 30-day trial version if used without a key – so you can right now go ahead and evaluate it.

MonitorWare Agent 9.3 Released (Build-IDs: Service 9.3.438, Client 9.3.1409)

MonitorWare Agent 9.3 Released

Build-IDs: Service 9.3.438, Client 9.3.1409

Features

  • Updated embedded OpenSSL library to 1.0.1h.

Bugfixes

  • SETP Protocoll: Fixed a bug in zlib decompression.
  • RELP Action: The RELP Action failed when no other network related Actions/services was configured.
  • Configuration Client: Fixed minor bugs in the configuration client.

You can download Free Trial Version of MonitorWare Agent.

Questions about Queues

Is the queue limit applied to all services or per service?

The queue limit is for all services combined. Be it a syslog listener, eventlog or file monitor. It does not differ between services, the memory queue is for all. The queue is basically to buffer message bursts that are higher than what MonitorWare Agent can forward/store. The default is 200000 log messages which can be stored in the memory.

What is better for TCP syslog forwarding – Diskqueue or Queue Diskcache?

The Queue Manager Diskcache is useful depending on whether you need high security. Beware, when enabling this, the queued messages will always be written to disk before processing. This will slow down the system a lot, depending on the speed of the harddrive. When forwarding via TCP syslog, using the diskqueue will store the messages to disk to prevent message loss in case the peer or the connection fails. This queue will only be used as needed contrary to the Queue Manager Diskcache which will be used always.

What is the recommended Queue limit?

The Queue Limit determines the amount of unprocessed messages that can be stored in the memory to allow message bursts to occur without the system stalling. Though, this needs to be tested with a real use-case and is mainly depending on the messages that are received per second and the messages that can be forwarded/written per second.