Configuration Guide
Configure DB24x7 to match your monitoring needs. Set up alerts, notification channels, performance thresholds, and manage your team.
Configuration Sections
Alert Configuration
Set up intelligent alerts for critical metrics
Performance Thresholds
Configure thresholds for performance monitoring
Notifications
Manage notification channels and preferences
Team Management
Add team members and manage permissions
Alert Configuration
Configure intelligent alerts to get notified about issues before they impact your users. DB24x7 uses machine learning to reduce alert noise.
Default Alert Types
These alerts are pre-configured with sensible defaults. You can customize thresholds for each database.
High CPU Usage
WARNINGAlert when CPU usage exceeds threshold
Memory Exhaustion
CRITICALAlert when memory usage is critically high
Slow Query
WARNINGAlert when queries exceed execution time
Connection Pool Full
CRITICALAlert when connection pool is nearly full
Replication Lag
WARNINGAlert when replica lag exceeds threshold
Disk Space Low
CRITICALAlert when disk space is running low
Configuring Alert Thresholds
Navigate to Settings → Alerts to configure thresholds:
- Select the database you want to configure
- Click on the alert type you want to customize
- Adjust the threshold value
- Set the evaluation period (how long condition must persist)
- Choose notification channels for this alert
- Save your configuration
# Example: CPU Usage AlertThreshold: 85%Evaluation Period: 5 minutesSeverity: WarningChannels: Email, SlackSmart Alerting
DB24x7's AI learns your database patterns and automatically adjusts alert sensitivity to reduce false positives. Enable "Smart Alerts" in settings to use dynamic thresholds based on historical behavior.
Performance Thresholds
Configure performance monitoring thresholds to track query performance, resource usage, and system health.
Query Performance
- Slow Query Threshold: 1000ms default
- Query Timeout: 30000ms default
- Lock Wait Threshold: 5000ms
Resource Limits
- CPU Warning: 80% usage
- Memory Warning: 85% usage
- Disk Warning: 80% usage
Replication
- Lag Warning: 30 seconds
- Lag Critical: 60 seconds
- Replica Down: Immediate alert
Connections
- Pool Usage: 90% warning
- Connection Errors: Track failed attempts
- Idle Connections: Monitor unused
Customizing Thresholds
Navigate to Settings → Performance Thresholds and configure each metric:
# Example Configurationslow_query_threshold: 2000 # millisecondscpu_warning_threshold: 75 # percentagememory_critical_threshold: 95 # percentagereplication_lag_warning: 45 # secondsNotification Channels
Configure multiple notification channels to ensure your team is alerted through their preferred method.
Receive alerts via email
Setup: Configure SMTP settings or use default email service
Slack
Send alerts to Slack channels
Setup: Connect your Slack workspace and select channels
SMS
Get critical alerts via SMS
Setup: Add phone numbers and configure SMS provider
PagerDuty
Integrate with PagerDuty for on-call
Setup: Connect PagerDuty account with API key
Webhooks
Send alerts to custom endpoints
Setup: Configure webhook URLs and payload format
Notification Preferences
- Alert Grouping: Group similar alerts within 5-minute windows to reduce noise
- Quiet Hours: Suppress non-critical alerts during specified hours
- Escalation: Auto-escalate unacknowledged critical alerts after 15 minutes
- Recovery Notifications: Get notified when issues are automatically resolved
Team Management
Add team members, manage roles, and control access to your database monitoring.
Adding Team Members
- Navigate to Settings → Team
- Click "Invite Team Member"
- Enter email address and select role
- Choose which databases they can access
- Send invitation
Team Roles & Permissions
Admin
- Full access to all features
- Manage team members and roles
- Configure billing and subscription
- Delete databases and data
Developer
- View all monitoring data
- Configure alerts and thresholds
- Execute query optimization
- View and export reports
Viewer
- View monitoring dashboards
- View alerts and incidents
- View reports (read-only)
- No configuration changes
Best Practices
- • Use the principle of least privilege - assign minimum required permissions
- • Regularly review team member access and remove inactive users
- • Use separate accounts for automation and integrations
- • Enable two-factor authentication for all admin users