Administration Guide
This guide covers the essential administrative tasks for managing your Gluesync deployment. For detailed performance tuning and optimization guidelines, see our Best Practices Guide.
Control Plane Overview
The Gluesync Control Plane, accessible via port 1717, provides centralized management of your entire deployment:
| Feature | Description |
|---|---|
Web UI |
Browser-based interface for configuration and monitoring |
REST APIs |
Programmatic access for automation and integration |
Notifications and alerts |
Central location for system alerts and status updates |
Agent Management
Auto-Discovery
-
Agents automatically discover and join the Core Hub cluster via UDP
-
Kubernetes deployments use direct Core Hub addressing
-
No manual configuration needed for standard deployments
|
Agents can be added dynamically - the system will automatically detect and integrate them. |
Connection Management
-
Default connection settings are optimized for most use cases
-
Advanced configuration available for specific needs
-
For detailed connection tuning, see Connection Management Best Practices
Pipeline Configuration
Entity Management
-
Configure data mappings between source and target
-
Set up filtering rules
-
Define transformation logic
Advanced Settings
-
Performance tuning options available
-
Security configuration
-
For detailed configuration guidelines, see Performance Optimization
Monitoring and Maintenance
Notification Center
-
Access via bell icon (🔔) in top navigation
-
Categorized by severity:
-
Errors (critical issues)
-
Warnings (potential problems)
-
Info (system updates)
-
Health Checks
-
Connection status monitoring
-
Resource utilization tracking
-
Performance metrics
|
For detailed monitoring setup, see Monitoring Guide. |
Backup and recovery operations
-
Run scheduled Automator backups for every Core Hub tenant, especially before and after configuration changes.
-
Keep backup bundles in the same secure vault as your infrastructure-as-code artifacts so you can rebuild clusters in new environments quickly.
-
Perform restore dry-runs in staging to ensure the exported YAML and ZIP files remain valid and that masked secrets have been re-populated via your secret manager.
-
Document who is responsible for backups and where the latest artifacts reside to avoid scrambling during incidents.
Additional Resources
| Resource | Description |
|---|---|
Detailed performance tuning and optimization guidelines |
|
Common issues and their solutions |
|
Setting up and using monitoring features |
|
Log configuration and management |
|
Always refer to our Best Practices Guide when making configuration changes to ensure optimal performance. |