How to setup MonitorWare Products to use MySQL as database?

How to setup MonitorWare Products to use MySQL as database?

Created on 2002-08-09 by Andre Lorbach.

To use a MySQL Database with WinSyslog, EventReporter or MonitorWare Agent, you need to install some components (If you haven’t) first. Go to If you don’t have any MySQL Server, download MySQL-3.23.5 for Windows for example (Or a newer version if there is one).

Most important, you need to download an install the ODBC Drivers (myodbc-2.50 for example) for MySql. This is needed, because WinSyslog will use a ODBC-Driver for MySQL to access the database.

Note: If you are upgrading from MonitorWare Agent 1.x to 2.x, you would need to creat the SystemEventsProperties table. If you are upgrading from 4.x to 5.x or higher you would need to create the SystemEventsProperties table. Similarly if you are upgrading from 5.x (or any other previous version) to 6.x or higher you would need to create the SystemEventsProperties table.

1. On your MySQL Server, create a new database. The script below shows you an example:

CREATE database MyWinSyslog;
CREATE table SystemEvents
SystemID int,
ReceivedAt datetime,
DeviceReportedTime datetime,
Facility int,
Priority int,
FromHost nvarchar (60),
Message text,
NTSeverity int,
Importance int,
EventSource nvarchar (60),
EventUser nvarchar (60),
EventCategory int,
EventID int,
EventBinaryData text,
CurrUsage int,
MinUsage int,
MaxUsage int,
MaxAvailable int,
InfoUnitID int,
SysLogTag varchar(60),
EventLogType varchar(60),
GenericFileName VarChar(60),
Checksum int NULL,
CustomerID int

CREATE table SystemEventsProperties
SystemEventID int NULL ,
ParamName varchar (255) NULL ,
ParamValue text NULL

GRANT ALL MyWinSyslog.* To “database username@YourDNS or machine ip” IDENTIFIED BY”YourPassword”;

2. After you install the ODBC components, you will need to add a new ODBC System DSN. See the screenshot below which shows you the first step of the Wizard:

3.The screenshot below shows how all values could be filled in. But this depends on your configuration and names:

4. Now configure a Database Logging action in WinSyslog. In the Screenshot below, I used the values I specified before.

I have an invalid source in my received syslog message – what to do?

I have an invalid source in my received syslog message – what to do?

Created on 2002-03-17 by Rainer Gerhards.

If I look at the received syslog message source system, I see invalid names like “su”, “root” and the like. These correspond to some part of the syslog message. In any case, it is not the real system name. What can I do to receive the correct name?

The problems stems from non syslog-RFC compliant systems. The syslog service does RFC compliant message parsing. Unfortunately, many existing systems are not compliant to the syslog RFC and format the message other then specified. As such, the syslog service picks up an invalid source system – simply because invalid information is where the source system should be.

Fortunately, the syslog server can be instructed to ignore the source system in the syslog message. This is the defaut mode for all installations after 2002-03-20. This is done with the “Take source system from syslog message”. If that check box is checked, the source is taken from the message as specified in the syslog RFC. If it is unchecked, it is determined based on the sending system.

Adiscon’s experience is that as of this writing only a limited number of systems support RFC compliant message formatting, so we recommend to uncheck this option.

2002-03-01 MonitorWare Agent 1.0 Final

MonitorWare Agent 1.0 Final

Release Date: 2002-03-01

Final, officially supported release.

352-001 Exam   ,
1z0-434 dumps   ,
OG0-091 Study Guides   ,
9A0-385 exam   ,
2V0-621D dumps   ,
9L0-012 exam   ,
70-346 test   ,
70-346 certification   ,
SY0-401 pdf   ,
JK0-022 pdf   ,
101 certification   ,
000-080 Study Guides   ,
810-403 test   ,
74-678 test   ,
70-178 pdf   ,
700-501 test   ,
70-486 certification   ,
ADM-201 certification   ,
9A0-385 test   ,
70-270 exam   ,
2V0-620 test   ,
70-410 dumps   ,
70-480 pdf   ,
210-065 dumps   ,
70-413 pdf   ,
70-246 Exam   ,
1Z0-804 Brain dumps   ,
70-243 pdf   ,
SY0-401 pdf   ,
9A0-385 certification   ,
70-243 Study Guides   ,
1Z0-051 dumps   ,
1Z0-060 pdf   ,
070-461 dumps   ,
70-461 dumps   ,
350-080 pdf   ,
70-178 certification   ,
640-692 dumps   ,
400-201 certification   ,
1Z0-051 pdf   ,
1z0-808 pdf   ,
70-462 dumps   ,
NSE4 certification   ,
NSE4 dumps   ,
300-320 test   ,

2001-12-19 MonitorWare Agent 1.0 Beta 2 released

MonitorWare Agent 1.0 Beta 2 released

Adiscon GmbH today announced the immediate availability the 1.2 beta 2 release of the MonitorWare Agent. The release has been available finished an made available a few days ago. After passing the first steps in reality, it is now publicly announced. Continue reading “2001-12-19 MonitorWare Agent 1.0 Beta 2 released”

2001-09-28 MonitorWare Agent 0.8 released

MonitorWare Agent Preview Released

Adiscon GmbH today announced the immediate availability the 0.8 preview release of the MonitorWare Agent. This is the first publicly available MonitorWare Agent release.

The MonitorWare Agent will be our flagship system monitoring product.”, says president Rainer Gerhards. “I am glad
interested customers can now have a sneak preview of what is coming.
” The 0.8 Preview release is not feature complete. New features will be introduced before the final release.

To learn more about MonitorWare’s design, we have decided to include an excerpt from Rainer Gerhards’ letter to beta testers. We hope this information is helpful.


As you can see the preview’s functionality bases on the current EventReporter and WinSyslog products. HOWEVER, all product parts have been completely rewritten to offer highest performance and flexibility. One goal was to enable us to include new additions into the engine quickly. We are very confident to have reached that goal. This enables us to move quickly from now on.

For those of you operating high volume logging environments, the MonitorWare Agent is specifically designed to handle *large* bursts of incoming messages without any packet loss. We are now running with a multitude of finely-optimized internal threads.


We very thoroughly investigated the .NET platform. We believe this platform will be a strong player in the future and provide added benefits to customers. HOWEVER, after our intense testing, we do NOT believe that .NET is at this time the right choice for building high performance, low impact monitoring agents.
There are a number of issues, one of them is that .NET requires Microsoft
Internet Explorer installed on the machine (and this in a recent version). It also has a much larger memory and processing time footprint. As such, we have decided to continue to develop the agent (the NT service) in high performance native C++. This decision will last for a long time.

On the client side, we do not see that many problems with .NET. In fact, we
see a number of immediate advantages here. Thus, we have decided that the clients – specifically the not yet available enterprise client – will be based on the .NET tools. Because all of the .NET solutions are currently in beta only, we will provide the MonitorWare Configuration Client as a VB 6 project. Later versions will be moved to .NET as soon as market permits. The Enterprise Console will most probably be developed in .NET natively.


Another major player, we took into deep consideration and analysis. We
already developed and tested the product under this environment. The final Agent release will most probably be Windows XP optimized but run fine on all other Windows NT platforms, too.


Due to public demand, we are currently very closely considering porting the service to Linux. It is not on top of the features list and will be re-evaluated after launching the initial final release. We expect to have at least limited monitoring functionality for Linux systems. As far as the Linux variant is involved, we will most probably support the Red Hat distribution.

The MonitorWare Agent 0.8 Preview releease is a free download found at our web site. Interested users should download and try out the version. Though it is a preview, it is fully supported. Support questions should be addressed to