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

# Server Event Logging: Track Every Action in Real Time

> Configure Solara's logging to capture message edits, deletions, member joins, role changes, voice events, and moderation actions across dedicated channels.

A complete audit trail is essential for any well-run Discord server. Solara captures a wide range of server events in real time and delivers them to dedicated log channels of your choosing. When something goes wrong — a deleted message, an unexpected role change, a suspicious join — you'll have the context you need to act quickly.

## Events logged

**Message edits and deletes**
Solara captures the original content of edited and deleted messages, including the author, channel, and timestamp. Even if a user deletes their own message, you'll have a record.

**Member joins, leaves, and bans**
Every time a member joins, leaves, or is banned, Solara posts a log entry with the member's name, ID, account age, and action timestamp. This is particularly useful for detecting ban evasion.

**Role changes and nickname updates**
Solara logs when a member's roles are added or removed, and when their nickname is changed. Each log entry shows the before and after state along with who made the change.

**Voice channel events**
Track when members join, leave, or move between voice channels. These logs help you spot unusual activity and understand how your community uses voice.

**Channel and server settings changes**
Any change to a channel's name, permissions, or settings — as well as server-level changes like region or verification level — is captured and attributed to the account that made it.

**Moderation actions**
Every ban, kick, mute, and warning issued through Solara is automatically logged with the responsible moderator, the target member, and the reason provided.

## Setting up log channels

<Steps>
  <Step title="Run /logs setup">
    Type `/logs setup` in any channel where Solara has access to begin configuration.
  </Step>

  <Step title="Select the event type">
    Choose the event you want to log — for example, `message-delete`, `member-join`, or `role-change`. Solara presents a list of all available event types.
  </Step>

  <Step title="Choose the destination channel">
    Select the channel where Solara should send log entries for this event type. You can use a single channel for all events or separate channels for each.
  </Step>

  <Step title="Repeat for each event type">
    Run `/logs setup` again for each additional event type you want to track. Each event type is configured independently.
  </Step>
</Steps>

<Tip>
  Use `/ignore-channel #channel` to exclude a specific channel from message logs. This is useful for bot spam channels or other high-volume channels where message logging would add unnecessary noise.
</Tip>

## Commands quick reference

| Command           | Description                                        |
| ----------------- | -------------------------------------------------- |
| `/logs setup`     | Configure a channel for a specific log event type  |
| `/logs disable`   | Disable logging for a specific event type          |
| `/audit`          | View the server's audit trail, optionally filtered |
| `/ignore-channel` | Exclude a channel from being logged                |

<Note>
  You can configure a separate channel for each event type. Keeping moderation logs, message logs, and member logs in distinct channels makes it much easier to find what you need during an incident.
</Note>