> 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/publish-your-docs.md).

# Kali Log Processor Setup

Docker contained log processing API service.

## VM Specifications

| Category         | Specifications                   |
| ---------------- | -------------------------------- |
| VM Software      | Virtualbox                       |
| OS Version       | Kali Linux 2025.2 AMD64          |
| RAM              | 2 GB                             |
| Storage          | 80 GB, Dynamic                   |
| CPU              | 1                                |
| Network Adapter  | NAT Network, DHCP, `10.0.2.0/24` |
| Containerization | Docker                           |
| Log Processor    | Fluentd                          |

## Update

```
sudo apt update
```

## Install and Configure Docker

**Docker prerequisites**

```
sudo apt install docker.io docker-compose
```

**Add user to `docker` group**

```
sudo usermod -aG docker $USER
```

## Install and Configure Fluentd 

```
docker pull fluent/fluentd:v1.19-debian
```

```
cd ~
mkdir Docker && mkdir Docker/fluentd
cd Docker/fluentd
```

Configuration, `fluentd.conf` for `fluentd` docker instance

```
<source>
  @type http
  port 9880
</source>

<match **>
  @type azure_loganalytics
  customer_id YOUR_WORKSPACE_ID
  shared_key YOUR_PRIMARY_KEY
  log_type CowrieLogs
</match>
```

The `Dockerfile` to (re)build the `fluentd` image with the **Azure Log Analytics** plugin installed

```
FROM fluent/fluentd:v1.19-debian
USER root
RUN gem install fluent-plugin-azure-loganalytics
USER fluent
```

(Re)build the `fluentd` image from the `DockerFile`

```
docker build -t fluentd-azure .
```

{% hint style="info" %}
Recommend building the image from the `Dockerfile` from the get go, rather than pulling it then rebuilding it - because it `docker` will create an entirely new image.
{% endhint %}

Run a `fluentd` instance mounting the config file and forwarding incoming traffic to container port

{% code overflow="wrap" %}

```
docker create --name "log_processor" -p 9880:9880 -v ~/Docker/fluentd:/fluentd/etc fluentd-azure -c /fluentd/etc/fluentd.conf
```

{% endcode %}

{% code overflow="wrap" %}

```
docker start log_processor
```

{% endcode %}

{% embed url="<https://hub.docker.com/r/fluent/fluentd/>" %}

{% embed url="<https://rubygems.org/gems/fluent-plugin-azure-loganalytics>" %}

{% embed url="<https://www.rubydoc.info/gems/fluent-plugin-azure-loganalytics/0.7.0>" %}


---

# 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/publish-your-docs.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.