Store and Forward

After MonitorWare Agent collects and filters data through its input services, actions determine what happens next.

Common destinations

MonitorWare Agent commonly uses these actions:

• Write to File for local archival or troubleshooting

• Database logging for structured storage and later analysis

• Forward Syslog for downstream syslog infrastructure

• Forward SETP for reliable transfer to Adiscon systems

• Mail or Start Program for alerting and operational response

Database setup paths

• Default supported schema: Tutorial: Store Data in the Default Database Schema

• Custom schema integration: Tutorial: Integrate MonitorWare Agent with a Custom Database Schema

Choosing the first destination

For first-time setup, writing to a file is usually the easiest verification path. For production deployments, forwarding or database storage is often more useful.

If reliable delivery across temporary outages matters, configure disk-backed queues where the action supports them.

For browser-based review of stored data, use Adiscon LogAnalyzer as a separate component. For the current split between service administration and browser-based review, see How Do Remote Administration and Browser-Based Log Review Fit Together?.