Devo: Troubleshooting/FAQ

This collector has different security layers that can detect both an invalid configuration and abnormal operation. This document will help you detect and resolve the most common errors.

  • ConnectionError: Error retrieving data from API with response code {status_code}. This pull iteration did not produce any results.

    The response status code is different to 200. The cause depends on the status code received. These are some of the most common status codes:
      • 401: Unauthorized. Invalid credentials.
      • 403: Forbidden. Not allowed to perform this action.
      • 404: Not found. Invalid endpoint URL.
      • 429: Too may requests. API’s Rate Limiter has been exceeded.
    • Solution: Depending on the value of the status code, solutions for the most common errors could be:
      • 401: Try valid credentials.
      • 403: Try some credentials with privileges to make these requests.
      • 404: Try a valid endpoint.
      • 429: Set the requests_per_second parameter in config file to a lower value.

  • LookupError: All lookups have been rejected. ETL aborted.
    The collected message has an unexpected format.
    • Solution: This errors are expected as some data sources will not match the expected and accepted format.
      See the ‘Troubleshooting’ Section of the full Recorded Future Devo documentation for up-to-date troubleshooting information
This content is confidential. Do not distribute or download content in a manner that violates your Recorded Future license agreement. Sharing this content outside of licensed Recorded Future users constitutes a breach of the terms and/or agreement and shall be considered a breach by your organization.
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more