Troubleshooting¶

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Customer Managed Applies to customer-managed instances of Alation

Test Connection Fails¶

If the test connection fails, make sure the access key, secret key, account ID, and AWS region are entered correctly in the connector settings page.

Metadata Extraction Fails¶

If metadata extraction fails and you get an AccessDeniedException, there is probably insufficient permissions or misconfigured IAM policies. Check your QuickSight user’s role, and verify IAM Policies.
If no folders are fetched, make sure the QuickSight shared folders are not empty.

Connector reports error “Data set type is not supported through API yet”¶

Issue: The connector responded with the error message The data set type is not supported through API yet (Service: AmazonQuickSight; Status Code: 400; Error Code: InvalidParameterValueException

Resolution: Check you are not attempting to catalog datasets in QuickSight created from a file upload, as these datasets are not supported by QuickSight’s DescribeDataSet API which is used by the connector.

Customer-Managed Alation Instances¶

Alation Connector Manager Logs¶

To tail:

docker logs -f agent

To write to a file:

docker logs agent >& agent.logs 2>&1

Connector Logs¶

Note

The alation_ypireti commands should be run from the Alation shell as the alation user.

To get the connector ID:

alation_ypireti list --fields id name

To get full logs:

alation_ypireti kratos --subcommand logs <connector_id>

To write logs to a file:

alation_ypireti kratos --subcommand logs <conector_id> > connector.log 2>&1

To write logs from specific date to a file:

alation_ypireti kratos --subcommand logs --since 2020-08-15 <connector_id> > connector.log 2>&1

Alation Agent Troubleshooting¶

For ACS customers using the Agent, refer to Troubleshoot the Agent for guidance.

OCF Troubleshooting¶

For more troubleshooting guidance for self-managed Alation deployments, refer to Troubleshooting.