2003-02-25 MonitorWare Agent 1.2

Tuesday, February 25th, 2003

MonitorWare Agent 1.2

  • New Scaleable Filterengine -The new filter engine as very powerful, you can build complex filter conditions like known from Microsoft Network Monitor. A note for existing MonitorWare Agent Users. After update, you have to start the MWAgent Client first. This is important, because it will automatically import your existing filters into the new Filter system. If you are new to this kind of filtering, I recommend that you read the Filter Conditions part of the manual before you start to play with the filters. (more…)

"A complete step by step guide on setting up EventLogMonitor Service

Monday, February 24th, 2003

How To setup EventLogMonitor Service

Article created 2003-02-24 by Rainer Gerhards.
Last Updated 2005-08-16 by Timm Herget.



Note: This guide was initially written for MW Agent, but the steps are the same in EventReporter.

1. First, right click on "Services", then select "Add Service" and then "Event
Log Monitor":

2. Once you have done so, a new wizard starts.

If the following Popup appears, please select "Create Service":

Again, you can use either the default name or any one you like. We will use
"My Event Log Monitor" 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.

Note
1:
The "Default RuleSet" has been automatically assigned as
the rule set to use. By default, the wizard will always assign the first rule
set visible in the tree view to new services. In our case, this is not correct
and will be corrected soon.

Note 2: If you want to generate reports (using Monilog) on the data via this service i.e. EventLogMonitor, then you have to press
the "Configure for Monilog" button and make the settings as shown in the screen-shot.


Note 3: If you want to generate reports (using MonitorWare
Console) on the data via this service i.e. EventLogMonitor, then you have to
uncheck the "Use Legacy Format" option. This is recommended. If you don’t
uncheck this option then meaningful reports aren’t generated (i.e. reports are
not properly consolidated by MonitorWare Console).

5. Now you must differentiate between clients and central hub server. In
clients use the "Forward " RuleSet we have created in Step 2, select it as rule
set to use. In central hub server select the "Database Logging" RuleSet we have
created in Step 3. Leave all other settings in their default.

Clients:

Central hub server:

6. Finally, save the change and start MonitorWareAgent. This procedure
completes the configuration of the syslog server.

MonitorWare Agent cannot dynamically read changed configurations. As such, it
needs to be restarted after such changes. In our sample, the service was not yet
started, so we simply need to start it. If it already runs, you need to restart
it.

With step 5 the client machines configuration has finished. All the next
steps are only concerned with the central hub server.

A complete step by step guide on setting up database logging action

Monday, February 24th, 2003

How To setup Database Logging Action

Article created 2003-02-24 by Rainer Gerhards.

1.
Start the MonitorWare Agent

2.
Again, you can select the language to use. And
again, I suggest using English, as this makes the guide easier to follow.

3.
Then define a new rule set, right click
"Rules". A pop up menu will appear. Select "Add Rule Set" from this
menu. On screen, it looks as follows:

4.
Then, a wizard starts. Change the name of the
rule to whatever name you like. We will use "Database Logging" in this
example. The screen looks as follow:


Click "Next". A new wizard page appears.

5.
Select only Database Logging. Do not select any
other options for this sample. Also, leave the "Create a Rule for each of the
following actions" setting selected. Click "Next". You will see a
confirmation page. Click "Finish" to create the rule set.

6.
As you can see, the new Rule Set "Database
Logging" is present. Please expand it in the tree view until the action level
of the "Database Logging" Rule and select the "Database Logging" action
to configure.

7.
Now click on the Data Sources (ODBC) button to
open the ODBC Data Source Administrator. Then choose the "System DSN" tab an
click the "Add" button to add a new System-DSN (Select the Microsoft Access
driver like in the screenshot below).

8.
In the next step, click the "Select button and go
to the MonitorWare Agent installation directory (Usual C:\program files\MonitorWare\Agent\)
and choose the sample database called sample97.mdb. After that name the new DSN
with "MyDatabaseDSN" like in the following screenshot and press OK.

9.
Now close the ODBC Data Source Administrator
and switch back to the MonitorWare Agent Client and insert "MyDatabaseDSN"
in the DSN field. Leave all other settings in their default and save the
changes.

350-060 certification   ,
70-177 certification   ,
70-178 certification   ,
70-243 certification   ,
70-246 certification   ,
70-270 certification   ,
70-410 certification   ,
70-411 certification   ,
70-412 certification   ,
000-017 certification   ,
000-080 certification   ,
000-089 certification   ,
70-347 pdf   ,
OG0-091 pdf   ,
JN0-102 pdf   ,
1Z0-051 pdf   ,
70-178 pdf   ,
70-980 pdf   ,
70-532 pdf   ,
220-901 pdf   ,
300-135 pdf   ,
210-260 pdf   ,
200-120 pdf   ,
CAS-002 pdf   ,
9L0-066 pdf   ,
NSE4 pdf   ,
NS0-157 pdf   ,

2003-02-24 MonitorWare Agent 1.2 Final Released

Monday, February 24th, 2003

MonitorWare Agent 1.2 Final Released

Adiscon today announced the immediate availability of MonitorWare Agent 1.2 Final. This version has a new powerful Filter-Engine which allows you to build very complex Filters like known from Microsoft Network
Monitor. For more details see below.  (more…)

2003-02-04 MonitorWare Agent 1.2 Beta 1 Released

Tuesday, February 4th, 2003

MonitorWare Agent 1.2 Beta 1 Released

Adiscon today announced the immediate availability of MonitorWare Agent 1.2 Beta 1.

This version has a new powerful Filter-Engine which allows you to build very complex Filters like known from Microsoft Network Monitor. For more details see below.  (more…)