MonitorWare Agent 1.1 Released
Adiscon today announced the immediate availability of MonitorWare Agent 1.1.
Continue reading “2002-09-20 MonitorWare Agent 1.1 Final Released”
Log Consolidator and Alerter
Adiscon today announced the immediate availability of MonitorWare Agent 1.1.
Continue reading “2002-09-20 MonitorWare Agent 1.1 Final Released”
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 http://www.mysql.com/downloads/index.html. 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
(
ID int IDENTITY (1, 1) NOT NULL,
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
(
ID int IDENTITY (1, 1) NOT NULL ,
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.
Adiscon today announced MonitorWare Agent 1.1 Release Candidate 1 (RC1).
Continue reading “2002-08-07 MonitorWare Agent 1.1 Release Candidate 1 released”
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.
Release Date: 2002-03-01
Final, officially supported release.
Adiscon GmbH today announced the immediate availability of MonitorWare
Agent 1.0 FINAL. After an extended beta period, the product is matured and available.
Continue reading “2002-03-01 MonitorWare Agent 1.0 Final released”
Adiscon today announced MonitorWare Agent 1.0 Release Candidate 1 (RC1).
Continue reading “2002-02-21 MonitorWare Agent 1.0 Release Candidate 1 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”
Much enhanced release, now feature complete. The numerous changes will not be listed separately as there are so many. The Beta 2 release is expected to be very close to the final production code.
This is the initial release for people to get a sneak preview. It is incomplete, but the implemented features work reasonable stable. This release is not intended for production use.