MonitorWare Agent automatically monitors Windows Event Logs. All Event Logs including the Windows 2000 specific extensions are fully processed. Application log file monitoring provides support for virtually any application that logs to a text file like Web server log files, Oracle error logs files or Windows application log files (like the DHCP log files).
Ping and Port Probe services allow monitoring of both local and remote systems and services. These services are not restricted to Windows machines only – virtually any existing service can be used with these probes. Good examples are LINUX based web and mail servers or firewalls. But our probes don't restrict you to an OS – even if you have a server running on a mainframe, MonitorWare can check its operational state.
Failing systems and services are detected and alerts are generated.
The Windows service monitor and disk space monitor services check the local machine. Failing services and low disk space are quickly detected and can be used to trigger notifications or even corrective actions before problems arise.
Events are accepted via a standard Syslog server and hence all of the Syslog-enabled devices can be included in the MonitorWare system. This includes popular devices like routers and switches as well as printers and a large number of UNIX / Linux based systems and applications. Virtually all currently existing network devices support Syslog – so MonitorWare Agent can monitor all of them.
To reach an even broader device range, MonitorWare Agent not only supports standard compatible Syslog but also it supports popular extensions like Syslog over.
The MonitorWare system is modular and highly scalable. If a single server is to be monitored, MonitorWare Agent can provide all monitoring and alerting needs. However, multiple MonitorWare Agents in a complex, hierarchical network can talk to each other and provide both local and central alerting and event archiving.
All incoming events – no matter what source they came from – can be stored persistently. Options include archiving in databases as well as log files.
Different features can be used to alert upon receiving certain information and even automatically start counter measures.
MonitorWare Agent is powerful and flexible rule engine processes all events based on a configured set of actions. An unlimited number of rules and actions allows tailoring to the specific needs.
MonitorWare Agent has no noticeable impact on system resources. It is specifically written with minimal resource usage in mind. In typical scenarios, its footprint is barely traceable. This ensures it can also be installed on heavily loaded servers.
MonitorWare Agent is written to perform robust even under unusual circumstances. The reliability of the product is proven since 1996.
MonitorWare Agent is easy to install and configure. Comprehensive step-by-step guides and wizards help administrators with setting up even complex systems.
Does your security policy enforce you to use non-standard ports? MonitorWare Agent can be configured to listen on any TCP/IP port for Syslog messages.
Windows Event Messages can be forwarded using standard Syslog protocol. Windows severity classes are mapped to the corresponding Syslog classes. Codes are fully supported.
The MonitorWare Agent client comes with "Send Syslog Test Message". This option enables you to check if Syslog Messages being sent properly to the destination or not.
Windows Event Messages can be forwarded using Adiscon proprietary SETP protocol. Windows Event Logs are monitored successfully as well.
A new feature added in Monitor Ware Agent. It allows receiving SNMP messages.
It connects to the FTP server and on receiving the response sends the QUIT command to terminate the connection. It saves the connection status and response replies.
It connects to HTTP server, receives response and sends the QUIT command to terminate the connection. The connection status and response are saved. It also keeps some additional properties to configure like URL and QueryString, Request Type, Use Secure HTTPs Protocol, Referer and User Agent.
It connects to an IMAP server, receives response and sends the QUIT command to terminate the connection. The connection status and response are saved.
It connects to NNTP (Usenet) server, receives the response and sends the QUIT command to terminate the connection. The connection status and response are saved.
It connects to POP3 (Usenet) server, receives and sends the QUIT command to terminate the connection. The connection status and response are saved.
It connects to SMTP (Usenet) server and sends the HELLO command that is automatically constructed by MonitorWare Agent on startup using the full qualified DNS name. The SMTP probe then receives the response and sends the QUIT command to terminate the connection. The connection status and response are saved.
Support for IPv6 is available in all network related facilities of the engine. All network related actions will automatically detect IPv6 and IPv4 target addresses if configured. You can also use DNS resolution to resolve valid IPv6 addresses. Network related Services can either use IPv4 or IPv6 as internet protocol. In order to support both protocols, you will need to create two services. The only exception is the RELP Listener, which uses IPv4 and IPv6 automatically if available.
Windows 2000*, XP, 2003, Vista, 2008, 7, 8, 10, 2012 and Windows 2016; Workstation or Server – MonitorWare Agent runs on all of them.
The MonitorWare Agent client comes with multiple languages ready to go. Out of the box, English, French and German are supported. Other languages will be added shortly. Languages can be switched instantly. Language settings are user-specific; so multiple users on the same machine can use different languages.
Friendly and Customizable User Interface
New Skinning feature has been added to MonitorWare Agent Client. New Cloning feature added to MonitorWare Agent Client helps to clone a Ruleset, a Rule, an Action or a Service with one mouse click. Move up and Move down function has been added for Actions in the MonitorWare Agent Client. Wizards have been enhanced for creating Actions, Services and RuleSets. And other minute changes!
Handling for low-memory cases
MWAgent allocates some emergency memory on startup. If the system memory limit is reached, it releases the emergency memory and locks the queue. That means not more items can be queued, this prevents a crash of the Agent and the queue is still being processed. Many other positions in the code have been hardened against out of memory sceneries.
Multithreaded Queue Engine
The Action processing engine is multithread enabled, which means that the overall processing performance will increase in larger environments and MWAgent will benefit from smp machines.
* Support for Windows 2000 and other EOL operating systems is only partially available. Only a minimal service installation may be possible. More details: Information for a Mass Rollout