Skip to main content
Last updated on

Troubleshoot the Netskope Logs connector

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page describes common errors you might encounter with the managed Netskope Logs connector and how to resolve them.

Netskope API token not valid​

Error message:

Invalid Netskope API token. Verify that the API token has not expired. If it has expired, create a new API token, re-edit the UC connection, and run the pipeline again.

Cause: The API token is missing, incorrect, or expired.

Solution:

  1. Confirm that the API Token in the Unity Catalog connection matches a current Netskope REST API v2 token.
  2. If the token expired, create a new token, update the connection with the new value, and run the pipeline again.

For details, see Configure authentication to Netskope.

Insufficient Netskope API token privileges​

Error message:

Insufficient Netskope API token privileges. Go to Settings > Administration > Administrators & Roles and provide the required View access to the role associated with the UC connection, then rerun the pipeline.

Cause: The token's role is missing View access to the events and alerts you want to ingest.

Solution:

  1. In Netskope, go to Settings > Administration > Administrators & Roles.
  2. Grant the role associated with the Unity Catalog connection View access to the events and alerts you want to ingest.
  3. Rerun the pipeline.

For details, see Configure authentication to Netskope.

Netskope API rate limit exceeded​

Error message:

Netskope API rate limit exceeded; will back off and retry.

Cause: Netskope returned an HTTP 429 response. Netskope rate-limits its REST API v2 endpoints. See Using the REST API v2 dataexport iterator endpoints.

Solution:

The connector automatically backs off and retries. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Netskope API token.

Netskope API temporarily unavailable​

Error message:

Netskope API temporarily unavailable, please try the pipeline again.

Cause: Netskope returned a transient server error (HTTP 500, 502, 503, or 504).

Solution:

The connector automatically retries. If the issue persists, wait, then run the pipeline again.

On this page