SylonSylon
All featuresActivity Logging
Activity Logging

Activity Logging

A searchable timeline of every meaningful event on your Discord server.

Overview

Every meaningful Discord event — member joins and leaves, role and nickname changes, voice sessions, moderation actions and guard blocks — is recorded and viewable in a filterable dashboard timeline. Answer 'who did what, when' on your server in seconds.

How it works

1

Capture

Sylon records events as they happen, with actor, target, reason and rich metadata attached to each entry.
2

Filter

The dashboard lets you filter by action type, user or date range, and drill into any entry for full detail.
3

Understand

Summaries by action, top actors and per-day trends turn raw events into a clear picture of server activity.

Key capabilities

Member join/leave and profile-change tracking
Role, nickname and channel event logs
Voice join/leave/move/mute/deafen history
Moderation and guard event history
Dashboard filters by action, user and date
Summary charts: by action, top actors, by day

Setup

1.Open the dashboard, go to the Activity Logging tab and enable it.
2.Set the channel where activity events are posted.
3.That is the whole setup — every event type is covered as soon as it’s on.
4.Optionally give it its own channel separate from message logs, since the volume and audience are different.

How it works in detail

What gets logged

Joins, leaves, role changes, nickname changes, voice channel activity and moderation actions are all recorded here, giving one continuous timeline of what happened in the server.

How it differs from message logging

Message Logging is about edited and deleted messages specifically. Activity Logging is everything else that happens to a member or the server — the two exist separately so each can have its own channel and audience.

Reading the log

Because every event type lands in the same channel by default, it doubles as a server history — useful when reconstructing what led up to an incident.

Settings

Log ChannelThe channel where the bot will send log messages for this feature.

Good to know

Sylon needs View Channel and Send Messages in the log channel, plus View Audit Log to attribute moderation-adjacent events correctly.
Voice activity is logged per join/leave, not continuously, so it will not flood the channel during a long voice session.
This log is separate from Guard — Guard acts on dangerous changes, this only records that they happened.

Frequently asked questions

Where do I view logs?

In the web dashboard under your server's Logs page, with filters and detail views.

Does it track voice?

Yes. Voice joins, leaves, moves, server-mute and deafen are all recorded.

How long is history kept?

Action logs are retained for up to a year, more than enough for audits and investigations.

Related features