Collect and Monitor Data

MonitorWare Agent can collect both event data and operational monitoring data. That breadth is one of the main differences between MonitorWare Agent and the more specialized manuals in this doc set.

Typical input sources

MonitorWare Agent commonly starts with one or more of these input service types:

• Event Log Monitor V2 for Windows Event Log channels

• Syslog Server for network devices and applications that send syslog

• SETP Server for reliable structured forwarding between Adiscon products

• File Monitor for text-based application logs

• probe and monitor services such as Ping Probe, Port Probe, Diskspace Monitor, CPU/Memory Monitor, and NT Service Monitor

If you run multiple input services, see How Do Port, Address, and Transport Conflicts Work for Input Services? before reusing a transport, IP address, and port combination.

A practical first design

For a first working deployment, keep the design small:

1. Choose one input service that collects the data you care about first.

2. Attach that input service to a dedicated ruleset.

3. Add one simple action, such as write to file or forward via syslog.

4. Verify that the expected events arrive.

This produces a baseline that is easy to test before you add more services, filters, and destinations.