v1.2.0 - Monitoring Controller Support

v1.2.0 - Monitoring Controller Support

🆕 New Features

Monitoring Controller Integration

• Added comprehensive support for monitoring-controller communication
• New ControllersService with complete API methods for controller management
• Full controller health monitoring and heartbeat functionality

📊 New Types Added

Controller Health & Heartbeat

• ControllerHealthInfo - Controller health status with resource usage tracking
• ControllerHeartbeatRequest - Structured heartbeat submission format
• ResourceUsageInfo - CPU, memory, disk, and network usage metrics
• ControllerHeartbeat - Database record type for heartbeat persistence

Regional Monitoring Infrastructure

• MonitoringRegion - Regional monitoring infrastructure management
• RegionStatus constants (Active, Inactive, Maintenance)
• RemoteCluster - Remote cluster coordination and management

Backward Compatibility

• Probe type alias maintains compatibility with existing monitoring-controller code

🔧 New Service Methods

ControllersService (client.Controllers)

• SendHeartbeat() - Submit controller heartbeats with health data
• RegisterController() - Register new controllers with the API
• GetControllerStatus() - Retrieve individual controller status
• ListControllers() - List all registered controllers
• UpdateControllerStatus() - Update controller operational status
• DeregisterController() - Remove controllers from registry

🏗️ Architecture Impact

This release enables the monitoring-controller to:

• ✅ Submit health and resource usage metrics via heartbeats
• ✅ Register and coordinate with the central API infrastructure
• ✅ Participate in regional monitoring coordination
• ✅ Manage remote cluster relationships
• ✅ Maintain full backward compatibility with existing probe infrastructure

🔄 Breaking Changes

None - this release maintains full backward compatibility.

📦 Dependencies

• Go 1.24+ required
• Compatible with existing Nexmonyx API infrastructure
• No new external dependencies

---

This release resolves the blocking issues for monitoring-controller build and deployment, enabling full controller health monitoring and coordination capabilities.