Skip to main content
Logging answers “what actually happened” after the fact. Vetox can record 148 distinct events, each configured independently.
Logging is free. Three options within it — showing who performed an action, posting via webhook, and the bulk setup tool — require Basic.

​
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.

Server

Moderation

Messages

Channels

Roles

Emote Zone

Voice

Threads

Events

AutoMod

Stage

Webhooks

Integrations

Giveaways

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.

​
Configuring an event

Every event is off by default and has its own settings.
A channel and a webhook are mutually exclusive. Setting one clears the other. You cannot send the same event to both.
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.
The Disabled Channels exclusion only exists on message events. There is no per-channel exclusion for voice, role or moderation events.

​
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. 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.
Category mode is almost always the right choice. Individual mode across a broad selection creates a very large number of channels — up to 148.

​
Saving

Only events you actually changed are sent, so saving a single toggle does not rewrite your whole configuration.
Dashboard Watcher records only enable and disable actions for logging. Changing a channel, webhook or colour is saved correctly but leaves no audit entry.

​
Choosing what to log

These are the ones you will actually go back and read.
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.
Members joining and leaving voice generates constant entries. Log these only if you specifically need them.
A webhook destination keeps working if the channel is renamed or moved, and posts without the bot needing send permission there. Requires Basic.

​
Troubleshooting

Check that Logging is switched on in Server Setup, then that the specific event is enabled and has a destination.
It requires Basic and is silently reset below that tier.
Same cause — webhook destinations require Basic.
They have no category tab. Use the All tab and search.
A small number of events ship without a display name. The event itself works normally.

Dashboard Watcher

Tracks changes made in the dashboard, rather than in Discord.

Moderation Tools

Review and lift punishments currently in force.