Fjord

Fjord Documentation

Modules

03

Activity log

Record important events clearly in the Discord channels you choose.

Included features

  • 89 supported event types
  • One shared log channel
  • Individually selectable logs

What can the activity log do?

The activity log records selected events on your server. Choose from 89 event types and set a Discord channel for the entries. This lets you review changes to messages and moderation activity.

Set up activity log

Enable or disable Activity log with the “Logging” switch, whether or not a channel is selected. Turning it off keeps the selected log channel. Selecting “No channel” automatically turns the switch off.

Activity Log captures selected events on the server and publishes them collectively to a designated Discord text channel.

Required Discord rights

View channel Manage webhooks Show audit log

View Channel and Manage Webhooks must be available in the selected log channel. “Show audit log” is required so that Fjord can record administrative processes and reliably assign the people carrying out them. Channel-related permission overrides can override a server-wide channel permission.

LoggingOptional

Turns the entire activity log on or off. Without activation, no selected events will be output.

Protocol channelRequired upon activation

Determines the text channel in which the entries are published. The channel must be accessible and writable for Fjord.

EventsAt least one mandatory

Each event type can be activated individually. If logging is switched on, at least one event must be selected.

Include botsOptional

Determines whether actions of other bots are also logged.

  1. Open the desired server in the dashboard and then Activity Log.
  2. Enable logging.
  3. Select a log channel.
  4. Activate at least one of the available events.
  5. If necessary, determine whether actions of other bots are included.
  6. Save the configuration.

Delivery via a webhook

The activity log publishes entries through a webhook rather than as ordinary bot messages. Fjord needs the Manage Webhooks permission in the log channel.

PublicationAutomatically

Detected activities are collected and then published via the webhook in the selected channel.

Collection intervalApproximately 2 minutes

New entries do not necessarily appear immediately. Fjord publishes the collected logs approximately every two minutes.

A delay of up to about two minutes is normal and does not mean that Activity Log is down.

Select events

There are 89 individually activated event types available. The search box searches their names and descriptions. Unnecessary events can be left off so that the log channel only contains relevant operations.

CategoryCaptured operations
MessagesEdits, single and multiple deletions, pins, reactions, and removed links or attachments.
Channels & PermissionsCreation, editing and deletion of channels as well as changes to channel permissions.
ThreadsCreation, editing and deletion of threads.
Roles & RightsRoles, role permissions, member roles and role order changes.
MembersJoin, Leave, Kick, Ban, Unban, Profile, Nickname and Timeout.
Voice & StageJoin, Leave, Move, Disconnect, Mute or Unmute, Stream, Camera and Stage Channels.
Servers & BoostsServer profile, security, community settings, ownership transfer and boost status.
InvitationsCreation, editing and deletion of invitations.
Apps & AutomationBots, integrations, app command permissions and webhooks.
Emojis, Stickers & SoundsCreate, edit and delete emojis, stickers and soundboard sounds.
Events & CommunityServer events, onboarding questions, onboarding and server guide.
Auto-Moderator & ModerationMember cleanup, auto-moderator rules and hits, quarantine, timeouts, warnings, and unassigned audit actions.
MonetizationSupported monetization requests and accepted terms.

At least one event must be switched on. Which selection makes sense depends on which processes should appear in the log channel.

Include bot actions

If Include bots is disabled, actions of other bots will not be logged. This prevents automatic processes from filling the log channel unnecessarily.

If the setting is activated, changes made by moderation, role or integration bots can also appear. The selected events continue to determine which types of actions are issued.

Availability of previous content

For edited or deleted messages, Activity Log attempts to show the previous and new status. However, the previous content is not always available.

If previous content is missing, Fjord marks it as unavailable in the log. All remaining information will still be output. When editing, for example, the new content can appear even though the previous content is missing.

An incomplete before/after does not mean that Activity Log is down. For data protection reasons, message content is not retained indefinitely.

Fix errors

ObservationExamination
An event does not appear immediately.Wait approximately two minutes. Entries are collected before publication.
Nothing appears even after the collection interval.Check whether logging and the appropriate event type are activated and whether the configuration has been saved.
The log channel cannot be selected.Check whether Fjord can see the channel and write there. Also note channel-related permission overrides.
The webhook is missing or not publishing anything.Check the Manage Webhooks permission in the log channel. Then select the channel again and save.
Bot actions are missing.Activate Include bots and check whether the appropriate event type is switched on.
The channel contains too many entries.Disable unnecessary events or exclude actions from other bots.
Previous message content is missing.The information could not be provided and is therefore marked as unavailable. This is not a defect.
The saved channel is no longer available.Select an existing text channel accessible to Fjord and save again.