Overview
The Error Console displays recent errors the Platform logged while sending requests to your web services. Use it to monitor, investigate, and resolve integration issues.
The Error Console is located under App Administration > Error Console in App Manager.
IMPORTANT: The Error Console displays only the 100 most recent errors. Older errors are removed as new ones are logged. To keep a longer history, retrieve errors through the Errors API and store them in your own systems.
Error Details
Each error in the console includes:
Service: The web service that received the request, if any, such as Authentication Service or Driver Status Service.
URL: The URL of the request sent to your web service, if any.
Date: The date and time the error was logged.
Below each error, a message describes what went wrong. Common errors may include:
Message | What it means |
|---|---|
The service returned HTTP status [ | Your web service responded, but with an error status. Check your service's logs for the cause. |
The service could not be contacted due to a network error: timeout | Your web service did not respond in time. Confirm the service is running and its URL in Service Config is correct. |
The JSON response does not conform to the schema. | Your web service responded, but the response body does not match the schema in the API documentation for that service. Compare your response against the documented fields and types. |
If you receive a message in the Error Console and are unsure of its meaning, please contact support@eleostech.com for further assistance. | |
Viewing an Error
Navigate to App Administration > Error Console within App Manager
Select an error to open its details
The details page shows the error message at the top, followed by the request the Platform sent and the response your web service returned:
Request: The web service that received the request, the request URL, the headers, the user who made the request, and the request body.
Response: The response headers and body your web service returned. The body often contains your service’s own error message, ELD error message, or invalid response schema. For invalid JSON, the details page highlights the cause and location of the error when possible.
NOTE: Sensitive headers, such as
AuthorizationandEleos-Platform-Key, are replaced with[scrubbed].
Troubleshooting Errors
Start with the response body, which often states the cause directly. For instance, a Driver Status Service error might show that your service failed while parsing data from another source. If errors began at a specific time, check the Audit Log for related changes made around then. A changed web service URL or Eleos Platform Key often explains a sudden increase in errors.
If you cannot determine the cause of an error, contact support@eleostech.com and include a screenshot of the error and its details page.