SigNoz/signoz · warning
unsupported
unsupported
Error message
not implemented
What it means
The noop licensing API's Activate HTTP handler always returns an 'unsupported' error. This implementation exists so the service compiles/runs when no real licensing backend is wired in; every endpoint is a stub.
Source
Thrown at pkg/licensing/nooplicensing/api.go:18
package nooplicensing
import (
"net/http"
"github.com/SigNoz/signoz/pkg/errors"
"github.com/SigNoz/signoz/pkg/http/render"
"github.com/SigNoz/signoz/pkg/licensing"
)
type noopLicensingAPI struct{}
func NewLicenseAPI() licensing.API {
return &noopLicensingAPI{}
}
func (api *noopLicensingAPI) Activate(rw http.ResponseWriter, r *http.Request) {
render.Error(rw, errors.New(errors.TypeUnsupported, licensing.ErrCodeUnsupported, "not implemented"))
}
func (api *noopLicensingAPI) GetActive(rw http.ResponseWriter, r *http.Request) {
render.Error(rw, errors.New(errors.TypeUnsupported, licensing.ErrCodeUnsupported, "not implemented"))
}
func (api *noopLicensingAPI) Refresh(rw http.ResponseWriter, r *http.Request) {
render.Error(rw, errors.New(errors.TypeUnsupported, licensing.ErrCodeUnsupported, "not implemented"))
}
func (api *noopLicensingAPI) Checkout(rw http.ResponseWriter, r *http.Request) {
render.Error(rw, errors.New(errors.TypeUnsupported, licensing.ErrCodeUnsupported, "not implemented"))
}
func (api *noopLicensingAPI) Portal(rw http.ResponseWriter, r *http.Request) {
render.Error(rw, errors.New(errors.TypeUnsupported, licensing.ErrCodeUnsupported, "not implemented"))
}
View on GitHub (pinned to 5069bf80b0)
Solutions
- Use a build that includes a real licensing provider (commercial build) if you need licensing
- Return 404/ignore these endpoints in self-hosted deployments
- Don't build automated flows against licensing endpoints when using the noop module
Defensive patterns
Strategy: try-catch
Try / catch
// client side: treat 4xx 'unsupported' from /license/activate as licensing-disabled
if resp.StatusCode >= 400 { log.Info("licensing not available in this build") } Prevention
- Feature-detect licensing endpoints before calling them
- Don't automate against licensing endpoints in OSS builds
When it happens
Trigger: Calling the license activation REST endpoint (POST to the licensing API) while the noop licensing module is registered instead of a real provider.
Common situations: Running the open-source/self-hosted build where licensing endpoints are intentionally disabled; hitting /license endpoints in local dev with the noop module loaded.
Related errors
AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28).
Data as JSON: /api/errors/56e063c61819ea5a.
Report an issue: GitHub.