SigNoz/signoz · error · basemodel.ApiError

couldn't search for cloudprovider ingestion key: status: %s,

Error message

couldn't search for cloudprovider ingestion key: status: %s, error: %s

What it means

The request to search for the cloud-provider ingestion key completed at the HTTP level but the response carried status != "success" with an error message. The gateway's own application-level error is surfaced with its status and error text.

Source

Thrown at ee/query-service/app/api/cloudIntegrations.go:235

	cloudProviderKeyName := fmt.Sprintf("%s-integration", cloudProvider)

	// see if the key already exists
	searchResult, apiErr := requestGateway[ingestionKeysSearchResponse](
		ctx,
		gatewayUrl,
		licenseKey,
		fmt.Sprintf("/v1/workspaces/me/keys/search?name=%s", cloudProviderKeyName),
		nil,
	)

	if apiErr != nil {
		return "", basemodel.WrapApiError(
			apiErr, "couldn't search for cloudprovider ingestion key",
		)
	}

	if searchResult.Status != "success" {
		return "", basemodel.InternalError(fmt.Errorf(
			"couldn't search for cloudprovider ingestion key: status: %s, error: %s",
			searchResult.Status, searchResult.Error,
		))
	}

	for _, k := range searchResult.Data {
		if k.Name == cloudProviderKeyName {
			if len(k.Value) < 1 {
				// Fail early if actual response structure and expectation here ever diverge
				return "", basemodel.InternalError(fmt.Errorf(
					"ingestion keys search response not as expected",
				))
			}

			return k.Value, nil
		}
	}

View on GitHub (pinned to 5069bf80b0)

Solutions

1. Read the surfaced searchResult.Error text — it states the gateway's reason
2. Verify gateway authentication material (license/service account) is valid
3. Retry after transient gateway errors
4. Contact SigNoz support if the gateway consistently reports errors for a valid license

Inspect searchResult.Status/Error surfaced in the message; retry transient gateway errors, escalate persistent auth/license ones.

When it happens

Trigger: getOrCreateCloudProviderIngestionKey performs a key search via the gateway and the gateway responds with an error status: auth failure on the gateway, license/account issues, or internal gateway errors.

Common situations: Expired gateway credentials, license limits reached, or a transient cloud-side failure during CloudIntegrationsGenerateConnectionParams.

Related errors

• couldn't create cloudprovider ingestion key: status: %s, err
• ingestion keys search response not as expected
• gateway_unsupported
• couldn't query for deployment info: error: %w
• couldn't unmarshal deployment info response: error: %w

AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28). Data as JSON: /api/errors/a0d5f5930e71d5dc. Report an issue: GitHub.