GramGroupsBot
EN RU Open bot →

Network logs

Telegram log delivery setup.

Network logs deliver moderation events to a Telegram destination chat.

The dashboard currently does not provide detailed event history browsing. The Logs page shows destination status and topic mapping count. Event delivery is Telegram-first.

Where to Configure

Dashboard path:

/settings

Section:

Network logs settings

Status page:

/logs

Who Can Configure Logs

Only these roles can save network log settings:

  • owner
  • admin

Managers can view log status but cannot update the destination settings.

Fields

Network log settings include:

  • Telegram log chat ID.
  • Chat type: supergroup, group, or channel.
  • Delivery mode: auto, per_chat_topic, or single_feed.
  • Whether the log chat is a forum with topics.
  • Enabled flag.

Destination Chat

Create or choose a Telegram group, supergroup, or channel for moderation logs.

Add GramGroupsBot to that destination. The bot must be able to post messages there.

For forum-topic delivery, use a forum supergroup and grant the bot enough rights to create topics.

The chat ID usually looks like:

-1001234567890

Paste that value into Telegram log chat id.

Delivery Modes

Auto

Internal value: auto.

If the destination is marked as a forum and a source group exists, GramGroupsBot tries per-chat topic delivery.

If topic creation or topic sending fails, it falls back to single-feed delivery.

Per-Chat Topics

Internal value: per_chat_topic.

For each source group, GramGroupsBot tries to create or reuse a forum topic in the destination chat. Events for that source group are sent to its mapped topic.

Topic names are based on the source group title and truncated to 128 characters.

If topic delivery fails, the system falls back to single-feed delivery.

Single Feed

Internal value: single_feed.

All moderation events are sent to the main destination chat.

Each message is prefixed with the source group title and chat ID.

Event Types

Network logs can receive these event types:

  • Message deleted.
  • Delete failed.
  • Welcome sent.
  • Welcome failed.

Reasons

Common reasons include:

  • Stop word.
  • Required word missing.
  • Link blocked.
  • Blocked user.
  • Rate limit exceeded.
  • Welcome message.

Message Contents

A log message includes:

  • Source group label.
  • Event type.
  • Reason.
  • Matched value when available.
  • Telegram user ID when available.
  • Event time.

In single-feed mode, the message also includes a source prefix:

Source: Example Group (-1001234567890)

Topic Mapping

When per-chat topics are used, the app stores topic mappings. The Logs page displays the number of mapped topics.

If a topic already exists in the mapping table, it is reused.

If no mapping exists, the bot tries to create a new forum topic.

Failure Handling

Moderation continues even if log delivery fails.

If Telegram delivery fails, the application logs a warning internally and continues. It does not block message deletion or welcome message processing.

Important Limitation

Detailed moderation event history is disabled in the dashboard. Configure Telegram network logs if operators need real-time visibility.