MonitorWare Knowledge Base

Hi, I've been going round in circles in your help file and I can't for the life of me get the ODBC logging working. I can't even tell if the product is doing anything at all.

I gather from the quick setup help that I need to make a ruleset first. OK, I go to RuleSets, Add, give it a name "new ruleset", Database Logging.

Then I go to Rulesets, "new ruleset", Actions. I set up a system dsn and enter the dsn name in the box that says dsn. I hit save.

Now I go to Services, Default syslog listener. I change the ruleset to use to "new ruleset" and hit save.

Then I restart the default syslog listener.

Now what? I checked the mdb file I defined in the dsn and it's empty. no tables, nothing.

I have cicso pix that's configured to send trap messages to my computer running syslog. I know it's working because if I open the Interactive syslog server I can see messages coming in.

what's the next step? which option have I not clicked? nothing is happening as far as I can tell. I've also tried file logging but no logfiles are being created. This product is pretty confusing....

ok, I figured it out. I created a blank mdb file and I kinda expected your software would automatically create the tables and fields needed to store data, but instead it does nothing by itself. Once I imported (using MS Access) the table structure from your default db included with the software it magically started running.

It'd be nice if your software would either create the table structure if it can't find a table or, at minimum, flash an error or something. anything. I hate software that does nothing when it doesn't work. I can't troubleshoot a brickwall.

Hi mike,

just for your information: the reason that the tables are not created by the product itself is that this way we can run with not officially supported database systems. However, the upcoming new clients will have the ability to create the table for you - but it must be manually initiated.

I will also file a work item so that proper error reporting is used when there is no table. In fact, I had assumed, there were.

Rainer Gerhards
Adiscon

Just for information: based on the work item, I received the feedback that a descriptive error message is already logged to the application event log. It says "table systemevents not found". This was verified with version 4.2, earlier versions may not log this (correctly).

Rainer Gerhards
Adiscon