Core concepts

Use this section to understand how rsyslog Windows Agent thinks about collected Windows events and how configuration objects interact.

Concept map

rsyslog Windows Agent processing follows this model:

1. An input service collects or receives an event.

2. The collected data becomes an information unit inside the product.

3. The rule engine evaluates the event against rules and filter conditions.

4. Matching actions forward, transform, or discard the event.

In plain language, you can read this as:

input service -> ruleset -> action

Canonical concept pages

• rsyslog Windows Agent Services
• Information Units
• Rules
• The Rule Engine
• rsyslog Windows Agent Filter Conditions
• rsyslog Windows Agent Actions

Why this matters

Understanding these concepts helps you:

• design rulesets with predictable behavior

• avoid duplicate or conflicting processing paths

• choose the right transport and action type for each receiver

• troubleshoot why an event did or did not match a rule