> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/suricata.md).

# Suricata

Scanner supports Suricata EVE logs, which contain information relevant to network intrusion detection. In order for Scanner to see them, you configure Suricata to write EVE JSON logs to local disk and use Fluentd to forward those logs into an S3 bucket that Scanner is linked to.

## Step 1: Publish to S3

Follow the Suricata documentation to configure it to export EVE JSON logs to a single file on local disk. See: [Eve JSON Output](https://docs.suricata.io/en/latest/output/eve/eve-json-output.html).

{% hint style="warning" %}
This can be quite the firehose of data, so make sure to set up log file rotation to prevent your hard disk from filling up. See the Suricata documentation here: [Rotate log file](https://docs.suricata.io/en/latest/output/eve/eve-json-output.html#rotate-log-file).
{% endhint %}

Follow the Fluentd documentation to configure it to read Suricata logs from the local file and write the logs to your S3 bucket. Make sure to configure the output format to be **JSON**. See the following Fluentd documentation articles:

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

## Step 2: Ingest via Scanner Collect

Follow the [Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md) guide to ingest logs from S3 via Scanner Collect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.