Skip to main content

Troubleshooting Monte Carlo 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: Resources from certain domains not getting cataloged

  • Cause: This issue generally happens when the Monte Carlo user associated with the API key that the collector uses to authenticate to Monte Carlo does not have permissions to a certain domain.

  • Solution: Ensure the user has access to the specific domains.

Issue 2: The collector may not complete successfully

  • Cause: Large deployments of Monte Carlo may result in API timeouts.

  • Solution: Lower page size for the parameter --montecarlo-graphql-page-size. The default is 250. Alternatively, adjust the --montecarlo-incident-lookback-days parameter to reduce the number of cataloged incidents.