Troubleshoot the Cribl connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Cribl from the Previews page. See Manage Databricks previews.
This page describes common errors you might encounter with the managed Cribl connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Authentication fails
Error message:
Authentication failed because credentials are missing or invalid.
Cause: Cribl.Cloud rejected the access token. The API Credential might be deleted, turned off, or have a rotated Client Secret.
Solution:
Confirm the API Credential is enabled in Cribl.Cloud, then update the connection with the current Client ID and Client Secret. See Configure authentication to Cribl.Cloud and Create a Cribl connection.
Insufficient permissions
Error message:
Insufficient permissions — Use credentials with access to this Worker Group/resource and retry.
Insufficient Permissions to access the requested resource.
API credentials don’t have permission to access system logs.
Cause: The API Credential lacks permission for the Worker Group, the Organization resource, or the Leader system logs that the table reads.
Solution:
Update the API Credential's Organization Permissions or Workspace permissions in Cribl.Cloud, or remove the affected table from the pipeline. See Create an API Credential.
Endpoint unavailable
Error message:
The requested endpoint is unavailable. Verify the request URL host and path.
Cause: The connector reached a host that does not serve the requested Cribl.Cloud API. The Workspace ID, Organization ID, or a host override is not valid.
Solution:
Verify the Workspace ID and Organization ID on the connection against your Workspace URL. If you set control_plane_host or management_plane_host, confirm the hostnames. See Find your Organization ID and Workspace ID and Connector options.
Rate limit exceeded
Error message:
Too many requests. Request rate exceeded the configured loginRateLimit or ssoRateLimit. Retry after a delay.
Cause: The connector exceeded the Cribl.Cloud API request rate.
Solution:
The connector retries automatically after the delay that Cribl.Cloud returns. If the error persists, reduce the pipeline schedule frequency or the number of pipelines that share the API Credential.
API temporarily unavailable
Error message:
API is temporarily unavailable or encountered an unexpected condition. Retry after a delay.
Cause: Cribl.Cloud returned a server error.
Solution:
The connector retries automatically. If the error persists, check the Cribl.Cloud status page, then rerun the pipeline.