> For the complete documentation index, see [llms.txt](https://kchuene.gitbook.io/data-communication-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kchuene.gitbook.io/data-communication-project/archive/wazuh-suricata.md).

# Wazuh Suricata

Installation of Wazuh for SIEM.

## Compose for Suricata

**Share Suricata logs volume for later log collection**

Edit `single-node/docker-compose.yml` under `wazuh.manager` service

{% code overflow="wrap" lineNumbers="true" %}

```yaml
services:
   wazuh.manager:
      volumes:
         - suricata-logs:/var/log:ro # Read-Only so we don't share our data
volumes:
   suricata-logs: # Add this line as well
      external: true
      name: suricata-logs
```

{% endcode %}

{% hint style="info" %}
The `suricata-logs` named volume should be (or should have been) created when composing **Suricata** container. Specifying it here will use the existing.
{% endhint %}

## Collecting Suricata Logs

**Edit Manager config**

In the **Wazuh Dashboard** navigate to **Server Management > Settings > Edit configuration** to edit the `ossec.conf` file to contain

{% code overflow="wrap" lineNumbers="true" %}

```
<ossec-conf>
   <localfile>
      <log_format>json</log_format>
      <location>/var/log/eve.json</location>
   </localfile>
</ossec-conf>
```

{% endcode %}

{% hint style="info" %}
Make sure to **restart** the **Wazuh Manager**. There should be a **Restart Manager** next to the **Save** button.
{% endhint %}

After restarting the container, confirm setting by navigating to **Server Management > Settings > Log data analysis > Log Collection**

{% embed url="<https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html>" %}

{% embed url="<https://documentation.wazuh.com/current/user-manual/wazuh-indexer/wazuh-indexer-tuning.html>" %}

{% embed url="<https://documentation.wazuh.com/current/user-manual/wazuh-indexer/re-indexing.html>" %}


---

# 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://kchuene.gitbook.io/data-communication-project/archive/wazuh-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.