Logging
118 events, routed exactly where you want them.
Ten categories covering the server, channels, roles, members, joins, messages, voice, moderation, integrations and Arclo's own actions. Route each event to its own channel, its category's channel, or one default — and see who did it, read from the audit log.
118 events, 10 categories, one router
Route per event, per category, or to one default channel. The event list on this page is the product's own, and every system logs its own actions through it.
Where logs go8 of 10 routed · 2 still need a channel
A message was deleted — with its content, its author and who removed it.
Needs audit logA message was edited, with the text before and after.
Someone was banned, with the moderator and the reason.
Needs audit logTwo or more messages were bulk-deleted. The whole batch is attached as a readable transcript.
Needs audit log118 events in 10 categories · every one can go to its own channel, with who did it from the audit log
What your members type
Commands are registered per server and only while the system is switched on — so a server that never turns this on never sees them in its command list.
/logs statusShows which log types are switched on, where each category is being sent, and anything blocking delivery.
/logs channelPoints a log category — or the server-wide default — at a channel.
/logs toggleSwitches a whole log category, or one individual log type, on or off.
/logs ignoreStops a channel, role, member or message prefix from ever appearing in the logs.
1 more command in Logging. Every one can be renamed, restricted to roles or switched off per channel from the dashboard — see the docs
More in Insight & control
Give your server its weekend back.
One all-in-one bot, 50+ systems, one dashboard, one login. Add Arclo and have your first system running before you finish this sentence.