Configuring

This section explains how to configure WinSyslog after installation. Use it to define input services, build rulesets and filter logic, configure actions, and verify that the WinSyslog service is receiving and processing messages as expected.

In this manual, input is the clearest plain-language concept for anything that receives logs, while service remains the main operational term for the configured WinSyslog object. Some GUI pages still use exact labels such as Syslog server or RELP Listener. Those are specific current client labels, not separate concepts. For the terminology mapping, see FAQ: What do “service”, “listener”, and “server” mean in WinSyslog?.

Recommended setup path

1. Define input services under Services and attach each service to a ruleset.

2. Build processing under Filter conditions (rules, filters, order).

3. Add actions under Actions to store and/or forward the data.

4. Verify reception with Send Syslog Test Message and a temporary “write to file” action.

• Core concepts
  • Concept map
  • Canonical concept pages
  • Why this matters
• Configuring WinSyslog
• Organizing with RuleSets, Rules, and Actions
• Client Options
• Client Tools
  • Syslog Test Message
  • Passive Syslog Receiver
  • Network Discovery
  • Kill Service
  • DebugLog
• Using File based configuration
• General Options
  • License
  • General
  • Debug
  • Engine
  • Queue Manager
  • Permitted Senders
• Services
  • Basic services
  • Network services
• Filter conditions
  • Default filter behavior
  • Building more selective filters
  • How to think about filter logic
  • Practical guidance
  • Filter condition reference pages
  • Basic filters
  • Network-related filters
  • Event and file monitoring filters
  • Custom property filters
• Actions
  • Storage actions
  • Forwarding and notification actions
  • Internal processing actions
  • Other actions