MonitorWare Knowledge Base

Hi to the Adiscon Team

When installing the Rolling Beta (2.2.233), the following problems are experienced with Event logging to the Database:
- The Message field contents are not logged for an agent where an upgrade was performed while it is logged on a clean install.
- The field EventCategory is logged as 0
- The field EventLogType is always an empty string (not null)
- NTSeverity is always -1

In short, it appears as if the database logging of Events has suffered from the recent changes.

Regards
Mark

While testing the new Echo reply functionality, the following problems were encountered:
- The following event log error is logged on MonitorWareAgent startup after a new "Echo Reply" was added: "No Rulebase found for service 'MonitorWare Echo Reply 3' - rule base requested was 'ℰ@'. This service NOT started." -> This, however, cannot be as there is no option to chose a RuleSet for this service type.
- When adding to devices to the list "Echo Request Devices", the messages returned are identical for any failure/success message, i.e. the failure always seems to occur for the first device (i.e. two messages with the same contents are logged when both devices are failing)
- The "Also Generate Event..." action produces the identical message as the failure message.

I hope this helps.

Regards
Mark

The CPU and Memory Monitors perform unexpectedly:
I have enabled the CPU check + also report when below and also the Memory Check, also report when below as well as "Handle Physical...". On every occurrance of the check, the following message is logged 4 times (when setup to write to the Event Log):
Total CPU Load = 9 %ERROR: invalid escape sequence!%

Regards
Mark

Hi Mark,

thanks for the detailled reports. Let me start with the CPU and Disk monitor.

This is actually not an issue with these monitoring services. The issue is with the "write to event log" action. This action needs to escape percent signs ("%"), what it obviously does not do. The result is the the Event Log API assumes there are parameters, which are not present. We will fix this as part of the next refresh. Consequently, if you use any other action, you will not see any problems.

We will look at your other questions soon.

Rainer