Admin Panel
The admin panel is an advanced view available exclusively to bot developers. It provides full insight into bot operation across all servers, system logs, usage statistics, and a broadcast system.
Access
The admin panel is available only to users defined as developers:
- User with ID set in the
DEVELOPER_USER_IDenvironment variable - Users added to the
developerstable in the database
Regular server administrators do not have access to this panel.
Global Statistics
The main panel section displays current bot statistics:
| Metric | Description |
|---|---|
| Total Guilds | Number of active servers with the bot |
| Total Users | Number of unique users (from command_stats) |
| Commands (24h) | Commands executed in the last 24 hours |
| Command Breakdown | Command ranking by usage frequency (24h) |
| Uptime | API process runtime since last restart |
| Last Restart | Last restart timestamp |
System Health
The panel displays infrastructure health metrics:
| Metric | Description |
|---|---|
| Bot Status | Online/Offline (checked via health check port 8080) |
| DB Size | PostgreSQL database size |
| DB Connections | Used/maximum connections in the pool |
| Process Memory | RAM used by the API process |
| System Memory | System RAM (used/total) |
| CPU | Processor load |
| Disk | Used/total disk space |
| Python Version | Python version on VPS |
| OS Info | VPS operating system |
Server List (detailed)
Table of all active servers with information:
- Server name (fetched from Discord API)
- Server icon
- Member count
- Language
- Embed color
- Enabled modules
- Installation date
Clicking a server opens the full configuration (cog_settings, dashboard_users, broadcast_channel, etc.).
Command Statistics
Charts and data about command usage:
- Daily statistics — command usage chart for a selected period (up to 90 days)
- Filter by command — view usage of a specific command
- Cog Usage — how many servers have a given module enabled
Operational Logs
System log table with filtering:
| Filter | Options |
|---|---|
| Severity | info, warning, error |
| Event Type | Event type (e.g., guild_join, config_update, error) |
| Limit | Maximum 500 entries |
Each entry contains: timestamp, severity, event_type, guild_id, message.
Broadcast System
Broadcasts are messages sent by the developer to all servers with the bot (to their broadcast channel).
Creating a Broadcast
- Select a category:
- changelog — update information
- announcement — announcements
- maintenance — planned downtime/maintenance
- Enter a title (max 256 characters)
- Optionally: add content (max 4000 characters)
- Optionally: use the visual embed editor
- Optionally: schedule for a specific time (scheduled_at)
- Send — the bot delivers the broadcast within 30 seconds
Broadcast History
Table of sent broadcasts with delivery reports:
| Field | Description |
|---|---|
| Title | Broadcast title |
| Category | changelog / announcement / maintenance |
| Sent At | When it was sent |
| Success Rate | % of servers it reached |
| Targeted | How many servers were targeted |
| Successful | How many deliveries succeeded |
| Skipped | How many were skipped (no channel) |
| Failed | How many failed (errors) |
Delivery Report
Clicking a broadcast shows details:
- How many servers were targeted
- How many deliveries succeeded
- How many were skipped (e.g., no broadcast channel)
- How many failed + error details
Developer Management
The panel allows managing the list of bot developers:
- List — all developers (from DB + env var)
- Add — new developer by Discord User ID
- Remove — remove developer (cannot remove yourself or the primary developer from env var)
The primary developer (from DEVELOPER_USER_ID) cannot be removed — this is a safeguard against losing access.