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

# Logging System

> Track server events and moderation actions with comprehensive logging.

# Logging System

Veronica's logging system provides detailed audit trails for server events, moderation actions, and member activity. Keep your staff informed and maintain accountability with customizable log channels.

## Quick Setup

<Steps title="Configuration Workflow">
  <Step title="Create Log Channels">
    Create dedicated channels like `#mod-logs`, `#server-logs`, and `#message-logs`.
    <Check>Log channels created with restricted staff-only permissions.</Check>
  </Step>

  <Step title="Initialize Logging">
    Run the setup command to link your channels.

    ```bash theme={null}
    /logging setup
    ```

    <Check>Core logging infrastructure initialized.</Check>
  </Step>

  <Step title="Toggle Events">
    Choose which specific actions you want to track.

    ```bash theme={null}
    /logging events
    ```

    <Check>Event tracking configured!</Check>
  </Step>
</Steps>

## Logged Events

<AccordionGroup>
  <Accordion title="Moderation Actions" icon="gavel">
    * Ban / Unban / Hardban
    * Kick / Softkick
    * Mute / Unmute / Timeout
    * Warn / Revoke Warn
    * Jail / Unjail
    * Purge / Clear
  </Accordion>

  <Accordion title="Server Events" icon="server">
    * Role created / deleted / updated
    * Channel created / deleted / updated
    * Server settings changed (Vanity, AFK, System)
    * Emoji added / removed
    * Webhook created / deleted
  </Accordion>

  <Accordion title="Member Events" icon="user-gear">
    * Member join / leave
    * Nickname changed
    * Roles added / removed
    * Avatar updated
  </Accordion>

  <Accordion title="Message Events" icon="message-slash">
    * Message deleted
    * Message edited
    * Bulk delete (Purge)
    * Pinned / Unpinned
  </Accordion>
</AccordionGroup>

## Configuration Examples

<CodeGroup>
  ```bash Set Mod Log Channel theme={null}
  /logging modlog channel:#mod-logs
  ```

  ```bash Set Server Log Channel theme={null}
  /logging serverlog channel:#server-logs
  ```

  ```bash Enable Message Logging theme={null}
  /logging messagelog enable channel:#message-logs
  ```

  ```bash Configure Events theme={null}
  /logging events
  # Opens interactive panel to toggle specific events
  ```
</CodeGroup>

## Log Format

Logs are sent as rich embeds with detailed information:

```
🔨 Member Banned
━━━━━━━━━━━━━━━━━━━━
👤 User: @BadUser (123456789)
👮 Moderator: @ModUser (987654321)
📝 Reason: Spamming
⏰ Timestamp: Jan 30, 2026 3:45 PM
🆔 Case ID: #1234
```

## Advanced Features

<AccordionGroup>
  <Accordion title="Case System">
    Each moderation action is assigned a unique case ID for easy reference and appeals.
  </Accordion>

  <Accordion title="Ignore Channels">
    Exclude specific channels from message logging (e.g., spam channels).

    ```bash theme={null}
    /logging ignore channel:#spam
    ```
  </Accordion>

  <Accordion title="Ignore Roles">
    Exclude specific roles from logging (e.g., bots).

    ```bash theme={null}
    /logging ignore role:@Bots
    ```
  </Accordion>

  <Accordion title="Log Retention">
    Configure how long logs are stored in the database.

    ```bash theme={null}
    /logging retention days:90
    ```
  </Accordion>
</AccordionGroup>

## Best Practices

<Note>
  Use separate channels for different log types to keep information organized and easy to review.
</Note>

<Warning>
  Ensure log channels have restricted permissions so only staff can view sensitive moderation information.
</Warning>

<Tip>
  Enable Auto-Mod logging to track automated actions and fine-tune your filters based on false positives.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Moderation" icon="gavel" href="/resources/commands">
    See how logged actions appear in practice with the moderation toolkit.
  </Card>

  <Card title="Permissions" icon="shield-check" href="/configuration/permissions">
    Ensure only staff can access your sensitive log channels.
  </Card>
</CardGroup>