Author: adisconteam

How To setup File Monitor Service

How To setup File Monitor Service

Article created 2006-12-21 by Florian Riedl.

1. First, right click on “Services”, then select “Add Service” and the “File Monitor”.

Once you have done so, a new wizard starts.

2. Again, you can use either the default name or any one you like. We will use “My FileMonitor” in this sample. Leave the “Use default settings” selected and press “Next”.

3. As we have used the default, the wizard will immediately proceed with step 3, the confirmation page. Press “Finish” to create the service. The wizard completes and returns to the configuration client.

4. Now, you will see the newly created service beneath the “Services” part of the tree view. To check its parameters, select it:

As you can see, the service has been created with the default parameters.

5. To make this Service work, we need to select a text file as source. To achieve this, click on the “Browse” button as you can see it marked in the screen above. A browsing window will open up. Move through your Files and choose one that you would like to monitor. For this example I chose a text file created by MonitorWare Agent.

6. Now we still need to set a ruleset for this service to work with. Since we have no configured ruleset available at the moment, simply use the Default Ruleset, if it’s not being used automatically.

7. Last, save the changes and then restart the application. This procedure completes the configuration of the FileMonitor Service.

The Application cannot dynamically read changed configurations. As such, it needs to be restarted after such changes.

How To setup FileMonitor Service

How To setup File Monitor Service

Article created 2006-12-21 by Florian Riedl.

1. First, right click on “Services”, then select “Add Service” and the “File Monitor”.

Once you have done so, a new wizard starts.

2. Again, you can use either the default name or any one you like. We will use “My FileMonitor” in this sample. Leave the “Use default settings” selected and press “Next”.

3. As we have used the default, the wizard will immediately proceed with step 3, the confirmation page. Press “Finish” to create the service. The wizard completes and returns to the configuration client.

4. Now, you will see the newly created service beneath the “Services” part of the tree view. To check its parameters, select it:

As you can see, the service has been created with the default parameters.

5. To make this Service work, we need to select a text file as source. To achieve this, click on the “Browse” button as you can see it marked in the screen above. A browsing window will open up. Move through your Files and choose one that you would like to monitor. For this example I chose a text file created by MonitorWare Agent.

6. Now we still need to set a ruleset for this service to work with. Since we have no configured ruleset available at the moment, simply use the Default Ruleset, if it’s not being used automatically.

7. Last, save the changes and then restart the application. This procedure completes the configuration of the FileMonitor Service.

The Application cannot dynamically read changed configurations. As such, it needs to be restarted after such changes.

2006-10-25 MonitorWare Agent 4.2 Final Released

MonitorWare Agent 4.2 Released

Adiscon is proud to announce the 4.2 release of MonitorWare Agent. This release contains a few features and some bugfixes. This is primarily a maintenance release. Find a list of changes below:

  • EventLog Monitor – A ressource library cache has been added. This new feature will mainly be useful for the Eventlog Monitor. All libraries will be cached for 30 minutes by default. For events with the same reoccuring event sources, this will be a great performance enhancement. The cache will also work for remote system libraries (requires administrative default shares).
  • Syslog Service, MonitorWare Echo Reply, SETP Receiver – TCP and UDP Services can now be bound to specific IP Addresses. This feature is useful for multihome environments where you want to run different Syslog Servers on different IP Addresses. Please note that the default IP Address 0.0.0.0 means ANY IP Address.
  • OpenSSL – Updated the OpenSSL components and libraries with the latest Version openssl-0.9.8d.
  • ForwardSyslog Action – Fixed a wrong Session Timeout value in case TCP was selected as protocol. This caused each TCP Session to be closed after usage. The session will now remain open for 30 minutes by default.
  • Database Service – Fixed a bug in the Database Monitor that caused saving the wrong LastID Value. Also fixed a bug in the Client that caused bogus error messages when a new Database Monitor was created.

More Details can be found in the version history

Version 4.2 is a free download. Customers with existing 3.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.

2006-10-25 MonitorWare Agent 4.2 Final (Build Service 4.2.316/Client 4.2.1062)

MonitorWare Agent 4.2 Released

Build-IDs: Service 4.2.316, Client 4.2.1062

New Additions

How to run MonitorWareLine Products on Windows Cluster Servers?

How to run MonitorWareLine Products on Windows Cluster Servers?

Created 2006-07-17 by Timm Herget

You want to run i.e. WinSyslog on a Windows 2003 Cluster but you are not sure if it will work properly on this platform and if there are any particular issues to be aware of in this configuration?

In our sample, we will use WinSyslog, but it also works with EventReporter or MonitorWare Agent.
From the technical point, WinSyslog can run on a Cluster-Node without any problems.
However there is no failsave or direct Cluster Support within WinSyslog.
This means in detail: if you want to run WinSyslog on other nodes, in case one node fails, you have to do the following:

Step 1

Set the Service Startup on all nodes to manual, expect on the node where you want to run WinSyslog mainly.


Figure1: setting service start to manual

To do so, go into the Windows Service Manager (Start -> Control Panel -> Administrative Tools -> Services) and look for the specific service name (in our case AdisconWINSyslog). Right click and select Properties from the upcoming dropdown menu. Set the startup type to manual, click apply and then ok.
Please note: Do not configure the Service to start manually on the main node!

Step 2

Mirror the configuration between the nodes manually by exporting & importing the configurations.


Figure2: mirror configuration

Our Products have the functionality to export an exact snapshot of the current configuration. This is done via standard Windows registry files. You can export your configuration on device a and import it on device b, which then has exactly the same configuration as device a.

To use it, please do the following:

  • Go to “Computer Menu”
  • Choose “Export Settings to Registry-File” (be sure NOT to select a binary format – they are only for special purposes. You can also NOT review binary files for security-relevant data.) Please also note that you can export in Win32 or x64 format so please choose the right one for your system.
  • Save this registry file.

Otherwise just install WinSyslog on your main node, it will run without any problems.

2006-07-10 MonitorWare Agent 4.1 Final (Build Service 4.1.312/Client 4.1.1038)

MonitorWare Agent 4.1 Released

Build-IDs: Service 4.1.312, Client 4.1.1038

New Additions

MonitorWare Agent 4.x – Database Structure

MonitorWare Agent 4.x – Database Structure

Created 2003-05-05 by Wajih-ur-Rehman.
Last Updated 2006-06-21 by Timm Herget.

What is the new Database Structure for MonitorWare Agent 4.x?

The Database Structure for MonitorWare Agent 4.x is almost the same as that of the older versions with the exception of SystemEventsProperties Table which is new in this new Database schema. In this new version, what the agent does is that it parses the message field and takes out some known parameters and store them in the form of name value pairs in the SystemEventsProperties Table as a Foreign Key. This means that one row in the SystemEvents Table can have multiples entries (in the form of name value pairs) in the SystemEventsProperties Table.

What is the log file format for generating reports with Monilog for MonitorWare Agent, WinSyslog and EventReporter?

What is the log file format for generating reports with Monilog for MonitorWare Agent, WinSyslog and EventReporter?

Created 2006-06-20 by Timm Herget

I am using MonitorWare Agent 4.x / EventReporter 8.x / WinSyslog 7.x
What are the settings that I would have to make such that the log file is generated in a format that is acceptable to Monilog?

There are a few things that have to be set in order to generate a log file that would be read by Monilog for Reporting purposes. Your settings would vary over:

  • 1. SETP Protocol
  • 2. Syslog Protocol

1. Report Settings for SETP

At Sender’s Side:

1.1. Event Log Monitor Setting

Use the default format of the EventLog Monitor’s. Your settings should be like this:


Figure 1: Event Log Monitor Service Settings

1.2. Forward Via SETP Settings

Use the default formtat of the “Forward via SETP” actions. In this example we assume that all messages should be forward via SETP to the central SETP Server at 172.16.100.8. Please replace this value per your environment.


Figure 2: Forward Via SETP Action Settings

At Reciever’s Side:

1.3. SETP Listener Settings

Use the default format of the SETP Server. Your settings should be like this:


Figure 3: SETP Listener Service Settings

1.4. Write to File Action Settings

In Write to File Action, Choose “Custom” from the “File Format” combo box. You would see that the “Custom Line Format” has been enabled. From the “Insert” menu entry select “Replace with Monilog Format“. Your settings should be like this:


Figure 4: Write to File Action Settings

With the above mentioned settings, Monilog will successfully generate the report on the log file that has been generated.

2. Report Settings for Syslog

At Sender’s Side:

2.1. Forward via Syslog Settings

In Forward via Syslog Action, you would see a “Message Format” option. From the “Insert” menu entry select “Replace with Monilog Format“. In this example we assume that all messages should be forward via Syslog to the central Syslog Server at 192.168.141.10. Please replace this value per your environment. Please Note: It is very important that you uncheck the “Add Syslog Source when forwarding to other Syslog servers” Option. Your settings should be like this:


Figure 5: Forward via Syslog Action Settings

At Reciever’s Side:

2.2. Syslog Listener Settings

Please note that the “Enable RFC 3164 Parsing” should be checked. Your settings should be like this:


Figure 6: Syslog Listener Settings
2.3. Write to File Action

Simply add a write to the file action and bind this RuleSet to the service. Do not chnage the default settings of this action!


Figure 7: Write to File Action Settings

With the above mentioned settings, Monilog will successfully generate the report on the log file that has been generated.

Guide For Applying Filters in MonitorWare Agent, WinSyslog and EventReporter – MonitorWare Agent

How do I apply filters in MonitorWare Agent 4.0?

Article created 2006-06-19 by Timm Herget.

MonitorWare Agent enables you to apply filters to achieve your desired results. This step-by-step guide helps you through creating these filters. You can: