Month: July 2003

How to use the Event Severity filter?

How to use the Event Severity filter?

Created 2003-07-29 by Andre Lorbach

The ‘Event Severity’ can be used to filter by event type. The following values are possible and valid:

EVENTLOG SUCCESS1
EVENTLOG ERROR TYPE2
EVENTLOG WARNING TYPE4
EVENTLOG INFORMATION TYPE8
EVENTLOG AUDIT_SUCCESS16
EVENTLOG AUDIT_FAILURE32

To filter by multiple event types, you can use an OR filter on the top level and multiple Event Severity filters below. In this sample, you wil see Event Severity with ERROR TYPE and WARNING TYPE:

2003-07-29 MonitorWare Agent 1.2 ServicePack 1

MonitorWare Agent 1.2 ServicePack 1

  • Configuration Client enhancements – Added two new filters, Event Category and Event Type. These two filters can be used for EventMonitor filtering.
  • Configuration Client bugfix – If a RuleSet was deleted, all RuleSets below the deleted one could lose their filter. This has been corrected now.
  • Syslog Service – New setting Enable RFC 3164 Parsing added. If this setting is disabled, MW Agent will not try to search for a SyslogTag in Syslog messages.

Adiscon products and the Microsoft SQL Server 2000 Desktop Engine

Adiscon products and the Microsoft SQL Server 2000 Desktop Engine

Created 2003-07-24 by Lutz Koch.

How do MSDE security risks relate to Adiscon products?

As a general policy, MSDE is *not* installed with any of our products.
Even though this may cause some additional setup work for customers, we have decided to do so because of vulnerability issues of MSDE. If you decide to install MSDE however, we think that you should be aware that you install a potentially dangerous, large piece of software.

If you are concerned on MSDE security, you may want to use MySQL instead of MSDE. We do offer full support for MySQL.