Load Wazuh data to DuckDB

Wazuh REST API provides endpoints to interact with the Wazuh manager, allowing for management tasks such as handling agents, monitoring status, and configuring security settings. Everything needed to build a working Wazuh → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Wazuh to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Wazuh to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Wazuh API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Wazuh API at a glance

These values come from the Wazuh API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Wazuh API?

The API requires a JSON Web Token (JWT) obtained via a POST request to /security/user/authenticate, which must be passed in the Authorization header as a Bearer token. Subsequent requests use the format 'Authorization: Bearer '.

1. Get your credentials

To obtain API credentials for the Wazuh REST API, use the following steps: 1. Identify your Wazuh API username and password (the default is 'wazuh:wazuh', though it should be changed for security). If you used the installation script, you can retrieve the password from 'wazuh-install-files.tar' by running: 'tar -axf wazuh-install-files.tar wazuh-install-files/wazuh-passwords.txt -O | grep -P "'wazuh'" -A 1'. 2. Authenticate to obtain a JSON Web Token (JWT) by sending a POST request to '/security/user/authenticate' with your Basic Auth credentials: 'curl -u <WAZUH_API_USER>:<WAZUH_API_PASSWORD> -k -X POST "https://<WAZUH_MANAGER_IP>:55000/security/user/authenticate?raw=true"'. 3. The returned JWT token is required in the 'Authorization' header ('Bearer ') for all subsequent API requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.wazuh_source]
wazuh_user = "wazuh"
wazuh_password = "your_password_here"
wazuh_api_url = "https://localhost:55000"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Wazuh data can I load into DuckDB?

These are the Wazuh endpoints dlt can load into DuckDB:

---

How do I load only new Wazuh records?

Wazuh exposes offset on agents, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "agents", "endpoint": {
    "path": "agents",
    "data_selector": "data",
    "incremental": {"cursor_path": "offset", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Wazuh pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /security/user/authenticate and /agents from the Wazuh API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def wazuh_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<WAZUH_MANAGER_IP>:55000",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "agents", "endpoint": {"path": "agents", "data_selector": "data"}},
            {"name": "rules", "endpoint": {"path": "rules", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_wazuh_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="wazuh_pipeline",
        destination="duckdb",
        dataset_name="wazuh_data",
    )
    load_info = pipeline.run(wazuh_source())
    print(load_info)


if __name__ == "__main__":
    load_wazuh_to_duckdb()

Run it with python wazuh_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Wazuh data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("wazuh_pipeline").dataset()
df = data.agents.df()
print(df.head())

SQL:

Copy
SELECT * FROM wazuh_data.agents LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Wazuh to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Wazuh loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Wazuh data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack