This repository was archived by the owner on Jan 4, 2026. It is now read-only.
Repository navigation
v2.3.1: Critical Fixes for Monitoring Controller
π Release v2.3.1 - Critical Fixes for Monitoring Controller
π― Overview
This release resolves critical blocking issues in the monitoring-controller CI/CD pipeline by making the IncidentsService and ProbesService properly available in the published SDK.
π§ What's Fixed
1. β IncidentsService Now Available
client.Incidentsis properly initialized with all required methodsCreateIncidentFromProbe(ctx, organizationID, probeID, probeName, description)- Create incidents from probe failuresResolveIncident(ctx, id)- Mark incidents as resolved- All incident data models included (Incident, IncidentStatus, IncidentSeverity, IncidentSource)
2. β ProbesService Now Available
client.Probesis properly initialized and accessible- Enables consistent API usage with
client.Probes.List() - Eliminates need for workaround
client.Monitoring.ListProbes()
3. β Version Update
- SDK version updated to v2.3.1
π Root Cause
The services were implemented but added after v1.3.1 was published. The monitoring-controller was trying to use features not available in the published SDK.
π¦ Installation
go get github.com/nexmonyx/go-sdk@v2.3.1π Migration Guide
-
Update your
go.mod:go mod edit -require=github.com/nexmonyx/go-sdk@v2.3.1 go mod tidy
-
Replace probe listing workaround:
// Old workaround: probes, _, err := client.Monitoring.ListProbes(ctx, nil) // New consistent API: probes, _, err := client.Probes.List(ctx, nil)
-
Enable incident creation:
incident, err := client.Incidents.CreateIncidentFromProbe( ctx, orgID, probe.ID, probe.Name, description )
β¨ Impact
- β Automated incident management restored
- β CI/CD pipeline unblocked
- β API consistency achieved
- β No operational blind spots
π Changelog
- Added ProbesService struct definition to client.go
- Verified both services properly initialized in NewClient()
- All required methods confirmed working
- Backward compatibility maintained
π Credits
Special thanks to the monitoring-controller team for the detailed bug report and requirements documentation.