> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noxus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Logging

> Centralized logging, audit trails, and troubleshooting for Noxus

Noxus implements a structured logging strategy to ensure that every event—from a user login to a complex flow execution—is recorded and searchable across your entire deployment.

## Logging Strategy

The platform follows a **structured logging** approach, emitting logs in JSON format to facilitate easy ingestion and analysis by modern log management systems.

* **Aggregation**: Logs are tagged by component (`noxus-backend`, `noxus-worker`, etc.) and workspace ID.
* **Correlation**: Every request is assigned a unique **Correlation ID**, allowing you to trace a single action across the frontend, backend, and worker pools.
* **Audit Trails**: Critical security and management actions are recorded in a dedicated audit log for compliance and forensic analysis.

***

## Collection Patterns

Noxus supports standard log collection patterns for both cloud and on-premises environments.

<Tabs>
  <Tab title="Kubernetes & OpenShift">
    **Native Log Routing**

    * Containers emit logs to `stdout/stderr`.
    * Use a sidecar or daemonset (e.g., FluentBit, Promtail) to forward logs to a central backend.
    * Automatic labeling of logs with namespace, pod, and container metadata.
  </Tab>

  <Tab title="VM / On-Premises">
    **Docker & Systemd Logs**

    * Collect logs via the Docker logging driver or `journald`.
    * Forward to a centralized destination using a lightweight agent.
  </Tab>
</Tabs>

***

## What We Log

To provide a complete picture of system activity, Noxus captures the following data points:

| Category               | Content                                                          |
| :--------------------- | :--------------------------------------------------------------- |
| **Flow Execution**     | Node starts/stops, input/output schemas, and execution timing.   |
| **Agent Interactions** | Conversation metadata, tool calls, and model reasoning steps.    |
| **System Events**      | Service lifecycle events, dependency health changes, and errors. |
| **Security Audit**     | Authentication attempts, role changes, and API key usage.        |

***

## Run-Level Logging & Archiving

In addition to centralized system logs, Noxus captures detailed execution logs for every individual **Agent** and **Flow Run**.

* **Execution Context**: These logs provide a step-by-step record of node executions, tool calls, and model reasoning for a specific run.
* **Cold Storage Archiving**: To ensure long-term availability and compliance, these run-level logs are autonomously archived in **Object Storage** (S3/GCS/MinIO) alongside the run's artifacts.
* **Accessibility**: Archived logs remain associated with their respective Run ID, allowing for historical review and forensic analysis even after the active execution state has been purged from the primary database.

<Warning>
  **Security First**: Noxus is configured to automatically redact sensitive information. However, ensure your log management system also follows strict data privacy policies. Never log raw secrets or full credential payloads.
</Warning>

***

## Troubleshooting with Logs

When investigating an issue, we recommend the following workflow:

1. **Identify**: Find the Correlation ID or Run ID associated with the error.
2. **Filter**: Search your log backend (Loki, Elasticsearch, Datadog) using the ID.
3. **Analyze**: Review the sequence of events across services to identify the point of failure.

<Card title="Monitoring" icon="gauge-high" href="/deployment/operations/monitoring">
  Combine logs with real-time metrics for a 360-degree view of your deployment.
</Card>