Skip to content
Mamba Host Docs

Discord Bot Operations & Scaling

Keep your Discord bot healthy in production with monitoring, scheduling, scaling strategies, and security best practices.

Monitoring & Alerting

Section titled “Monitoring & Alerting”

Panel Metrics

Section titled “Panel Metrics”

Monitor these key indicators in your panel:

MetricWarning ThresholdAction
RAM Usage> 75% sustainedOptimize caches or upgrade plan
CPU Usage> 90% spikesReduce workload or upgrade plan
NetworkUnusual spikesCheck for rate limit issues

  1. Check panel metrics regularly for RAM and CPU usage

  2. Download console logs or stream to external services (Logtail, Datadog)

  3. Subscribe to status webhooks at status.mambahost.com

  4. Set up heartbeat commands to report uptime to a monitoring channel

Scheduling & Automation

Section titled “Scheduling & Automation”

Common Scheduled Tasks

Section titled “Common Scheduled Tasks”
TaskFrequencyPurpose
RestartsDaily/WeeklyClear memory leaks
Dependency updatesWeeklyKeep libraries current
Database backupsDailyPrevent data loss
Log rotationDailyManage disk usage

  1. Schedule restarts during low-traffic windows

  2. Add update scripts (e.g., npm run update) followed by restart

  3. Use built-in scheduler for cron-style tasks

  4. Automate backups with mysqldump or SQLite copies to /backups

Scaling Strategies

Section titled “Scaling Strategies”

Vertical Scaling

Section titled “Vertical Scaling”

Move up tiers when resources are constrained:

FromToWhen
StarterProRAM/CPU > 75% sustained
ProPremiumNeed MySQL, PM2, or AI workloads

Horizontal Scaling & Sharding

Section titled “Horizontal Scaling & Sharding”

  1. Divide workloads by feature — separate bots for moderation vs music

  2. Use Discord’s sharding for guilds > 2,500

  3. Share state via Redis or MySQL across containers

  4. Keep slash-command registration aware of shard counts

Sharding Examples

Section titled “Sharding Examples”

Discord.js:

const { ShardingManager } = require('discord.js');
const manager = new ShardingManager('./bot.js', {
  totalShards: 'auto',
  token: process.env.DISCORD_TOKEN
});
manager.spawn();

Python (Disnake):

bot = commands.AutoShardedBot()

Multi-Environment Strategy

Section titled “Multi-Environment Strategy”
Section titled “Recommended Setup”
EnvironmentPurposeToken
DevelopmentLocal testingDev bot token
StagingPre-production testsStaging bot token
ProductionLive usersProduction bot token

  1. Mirror production env vars except for tokens/guild IDs

  2. Register slash commands in a staging guild first

  3. Run smoke tests before promoting to production

  4. Automate promotions from staging after tests pass

Data Management

Section titled “Data Management”

Database Options

Section titled “Database Options”
TypeBest ForPlan
SQLiteSmall bots, simple storageAny
MySQLInventories, audit logs, economyPro/Premium
Redis/UpstashCaching, rate limitingExternal service

Best Practices

Section titled “Best Practices”

  1. Back up SQLite — copy .db file nightly

  2. Request MySQL via support for Pro/Premium plans

  3. Use external Redis for frequently accessed data

  4. Offload large assets (images, audio) to S3-compatible storage

Cost Management

Section titled “Cost Management”
StrategyImpact
Monitor resource graphsIdentify optimization opportunities
Downgrade if utilization < 30%Reduce costs during low activity
Consolidate lightweight botsUse PM2 on Premium for multiple bots
Offload CPU-heavy tasksUse serverless workers for processing

Security Best Practices

Section titled “Security Best Practices”

  1. Rotate tokens when staff changes — remove old tokens immediately

  2. Use least-privilege OAuth scopes — only enable required intents

  3. Enable MFA on all panel accounts

  4. Create sub-users with scoped permissions instead of sharing root access

  5. Log sensitive actions (bans, payouts, command escalations) to immutable storage

Incident Response

Section titled “Incident Response”

  1. Detect — Watchdog restarts, 5xx errors, or alerting webhooks

  2. Stabilize — Scale up, disable problematic features, or roll back

  3. Communicate — Post in your community status channel

  4. Postmortem — Document timeline, root cause, and follow-up tasks

Incident Template

Section titled “Incident Template”
Incident: <Short description>
Detected: <Timestamp + monitoring source>
Impact: <Commands failing / downtime length / affected guilds>
Immediate Action: <Scale, rollback, disable feature>
Root Cause: <Once found>
Follow-up Tasks: <Testing, automation, docs>

Operations Checklist

Section titled “Operations Checklist”

Use this checklist for regular maintenance:

  • Monitor metrics weekly and adjust tiers accordingly
  • Review env vars quarterly — remove unused secrets
  • Test backups/restore monthly
  • Keep CI pipelines green before every deploy
  • Maintain a staging container for smoke tests
  • Document incident procedures and share with staff
Section titled “Helpful Links”
Discord Bot Overview Platform features and architecture
Deployment Guide Upload code and configure secrets
Troubleshooting Fix common errors and crash loops
Panel Guide Learn panel features

Need Help?

Section titled “Need Help?”