Troubleshooting Confluent Cloud collector issues
Collector runtime and troubleshooting
The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.
If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.
A list of common issues and problems encountered when running the collectors is available here.
Issue 1: The collector is unable to connect to Kafka
Cause: The provided Kafka information or credentials are not correct.
Solution: Check the server / base URL information and API key/secret are correct..
Issue 2: The collector does not harvest Confluent Kafka schemas
Cause: The provided Schema Registry information or credentials are not correct.
Solution: Check base URL information and api key/secret are correct, and permissions are properly set.