# Syslog

Scanner supports Syslog, which is a standard protocol used for message logging in various systems, especially in network devices and Unix/Linux-based systems. Many security tools emit Syslog data.

In order for Scanner to receive Syslog events, you need to configure a worfklow to push these logs to an S3 bucket that Scanner is linked to.

## Step 1: Publish to S3

We recommend running Fluentd to receive Syslog data over the Syslog protocol and forward it to your S3 bucket, writing output files in JSON format.

You can follow the Fluentd documentation to configure it to receive Syslog input and write output logs to your S3 bucket. Make sure to configure the output format to be **JSON**. See the following Fluentd articles:

* [Fluentd syslog input module](https://docs.fluentd.org/input/syslog)
* [Fluentd s3 output module](https://docs.fluentd.org/output/s3)

When you configure your `syslog` input module, in the parsing section, make sure to set `keep_time_key` to `true` so that Fluentd adds a `time` field to your log events. See: [Fluentd syslog parser module - keep\_time\_key](https://docs.fluentd.org/0.12/parser/syslog#keep_time_key).

## Step 2: Ingest via Scanner Collect

Follow the instructions [here](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/custom-logs-aws-s3) to ingest logs from S3 via Scanner Collect


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/syslog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.