Network logs send moderation events to a separate Telegram group or channel. The dashboard is a status and control page; delivery itself is Telegram-first.
Set Up a Log Destination
- Create a separate Telegram group or channel for operators.
- Add GramGroupsBot as an administrator and allow it to post messages.
- Send this command in that destination chat:
/logs
- Open the dashboard status page:
/logs
The Telegram command configures that chat as the destination. The dashboard lets you check the destination and enable, disable, or remove delivery.
Only account owners and admins should configure the destination. Keep the log chat separate from public discussion.
Current Delivery Model
The current user-facing command configures one shared feed (single_feed). Topic and automatic-routing modes exist in internal code paths but are not options in the public dashboard, so they are not part of the supported setup flow.
Every delivered event identifies its source group, so operators can distinguish events from different communities in the same feed.
What Is Logged
Network logs can include:
- message deletion and deletion failures;
- welcome-message delivery and delivery failures;
- the source group;
- rule reason and matched value when available;
- Telegram user ID when available;
- event time.
Common reasons are stop words, missing required words, blocked links, blocked users, and rate limits.
If Logs Do Not Arrive
Check the following:
/logswas sent in the intended destination chat.- The bot is still an admin there and can post messages.
- Log delivery is enabled on the dashboard
/logspage. - A real moderation event was produced by a connected active group.
Failure to deliver a log must not block the moderation action itself. For rule-level diagnosis, see Troubleshooting.