> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Logging Overview

> The available logging channels (Syslog, email, file) and the order in which to configure them.

<Tip>
  **Connecting a SIEM?**

  Start with [Connect a SIEM](/latest/integrations-siem). It covers which events are worth forwarding, which payload format to pick, and where to look in the documentation of Splunk, Microsoft Sentinel, QRadar, Elastic, and others — then sends you back here for the configuration.
</Tip>

Follow these steps:

1. Go through [Before You Begin](/latest/logging-before-begin).

2. Follow the guide that matches your desired integration:

   * [Logging via Syslog](/latest/logging-via-syslog)
   * [Logging via Email](/latest/logging-via-email)
   * [Logging via File](/latest/logging-via-file)

## Additional information

The guides above give you all information necessary to enable logging. However, here are some additional tips for Logging:

* xorlab logging is built with the open-source Logback framework. For more details on Logback, refer to the [Logback Documentation](http://logback.qos.ch/manual/appenders.html).

* You can use multiple `appender` in one `logback-audit.xml` file. The same `appender` can be used in multiple `logger` (for example to log the same event via multiple channels).

* You can use multiple `logger` in one `logback-audit.xml` file. The logger `name` attribute is hierarchical: For example, `name="audit"` will log all `audit.*` events.

* `appender` must be configured before `logger` in the `logback-audit.xml` file.

For worked configurations covering common logging use cases, see [Logging Examples](/latest/logging-examples).

For more conceptual information and references, have a look at:

* [Logging Concepts in xorlab](/latest/logging-concept)
* [Available Log Events](/latest/logging-events)
* [Available Log Formats](/latest/logging-formats)