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

# Logging

> Record 148 different server events to Discord channels or webhooks, each with its own channel and colour.

Logging answers "what actually happened" after the fact. Vetox can record **148 distinct events**, each configured independently.

<Info>
  Logging is free. Three options within it — showing who performed an action, posting via webhook, and the bulk setup tool — require **Basic**.
</Info>

## The screen

A tab strip with **All** plus fourteen categories, each showing how many of its events are enabled. Every tab has a search box and a running count of enabled events.

<CardGroup cols={3}>
  <Card title="Server" icon="server" />

  <Card title="Moderation" icon="gavel" />

  <Card title="Messages" icon="message" />

  <Card title="Channels" icon="hashtag" />

  <Card title="Roles" icon="user-tag" />

  <Card title="Emote Zone" icon="face-smile" />

  <Card title="Voice" icon="microphone" />

  <Card title="Threads" icon="comments" />

  <Card title="Events" icon="calendar" />

  <Card title="AutoMod" icon="filter" />

  <Card title="Stage" icon="podium" />

  <Card title="Webhooks" icon="link" />

  <Card title="Integrations" icon="plug" />

  <Card title="Giveaways" icon="gift" />
</CardGroup>

<Warning>
  **Four Battle Pass log events have no category.** Tier unlocked, season started, season ended and quest completed exist and work, but they are only reachable through the **All** tab — no category tab contains them.

  A handful of other events also display without a translated name.
</Warning>

## Configuring an event

Every event is **off by default** and has its own settings.

| Setting               | Default        | Notes                                                           |
| --------------------- | -------------- | --------------------------------------------------------------- |
| **Enabled**           | Off            |                                                                 |
| **Destination**       | Channel        | Toggle between a channel and a webhook                          |
| **Log Channel**       | None           | Where the entry is posted                                       |
| **Webhook URL**       | None           | Must be a Discord webhook URL. **Basic tier**                   |
| **Log Color**         | A default blue | Any hex colour                                                  |
| **Disabled Channels** | None           | Exclude specific channels. **Only on the nine Messages events** |
| **Show Executor**     | Off            | Include who performed the action. **Basic tier**                |

<Warning>
  **A channel and a webhook are mutually exclusive.** Setting one clears the other. You cannot send the same event to both.
</Warning>

<Warning>
  On Starter, **Show Executor** and **Webhook URL** are **silently reset when you save** — no error, no warning, the value simply reverts.

  If those two settings will not stick, that is why. Everything else on the event saves normally.
</Warning>

<Note>
  The **Disabled Channels** exclusion only exists on message events. There is no per-channel exclusion for voice, role or moderation events.
</Note>

## Setting up many events at once

Configuring 148 events individually is impractical, so **Manage Logs** creates channels and wires up events in bulk. Requires **Basic**.

| Mode                    | Result                                          |
| ----------------------- | ----------------------------------------------- |
| **Individual Channels** | A separate channel per event                    |
| **Category**            | One channel per category, under a Logs category |

You also choose which roles may view the created channels, and which channels to exclude. Created channels deny `@everyone` and grant only the roles you nominate.

The dialog reports progress through creating channels, assigning logs, setting permissions and applying exceptions.

<Tip>
  **Category mode is almost always the right choice.** Individual mode across a broad selection creates a very large number of channels — up to 148.
</Tip>

## Saving

Only events you actually changed are sent, so saving a single toggle does not rewrite your whole configuration.

<Note>
  [Dashboard Watcher](/en/server-management/dashboard-watcher) records **only enable and disable actions** for logging. Changing a channel, webhook or colour is saved correctly but leaves no audit entry.
</Note>

## Choosing what to log

<AccordionGroup>
  <Accordion title="Start with moderation and server events" icon="star">
    These are the ones you will actually go back and read.
  </Accordion>

  <Accordion title="Message events are high volume" icon="triangle-exclamation">
    Edit and delete logging on a large active server produces an enormous amount. Use the disabled-channels option to exclude your busiest channels — this is the one category where you can.
  </Accordion>

  <Accordion title="Voice events are noisier than they look" icon="volume-high">
    Members joining and leaving voice generates constant entries. Log these only if you specifically need them.
  </Accordion>

  <Accordion title="Webhooks survive channel changes" icon="link">
    A webhook destination keeps working if the channel is renamed or moved, and posts without the bot needing send permission there. Requires Basic.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing is being logged">
    Check that Logging is switched on in [Server Setup](/en/server-management/setup), then that the specific event is enabled and has a destination.
  </Accordion>

  <Accordion title="Show Executor keeps switching itself off">
    It requires Basic and is silently reset below that tier.
  </Accordion>

  <Accordion title="I set a webhook and it reverted to a channel">
    Same cause — webhook destinations require Basic.
  </Accordion>

  <Accordion title="I cannot find the Battle Pass log events">
    They have no category tab. Use the All tab and search.
  </Accordion>

  <Accordion title="An event has a blank or odd name">
    A small number of events ship without a display name. The event itself works normally.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Dashboard Watcher" icon="desktop" href="/en/server-management/dashboard-watcher">
    Tracks changes made in the dashboard, rather than in Discord.
  </Card>

  <Card title="Moderation Tools" icon="gavel" href="/en/moderation/moderation-tools">
    Review and lift punishments currently in force.
  </Card>
</CardGroup>