Reviewing the job - Amazon Lookout for Equipment
Checking the logs

Amazon Lookout for Equipment will no longer be open to new customers starting on October 17, 2024. If you would like to use the service, please sign up prior to October 17. For capabilities like Lookout for Equipment explore our blog post.

Reviewing the job

Few datasets are perfectly formed. Missing or incorrectly formatted values are common. Therefore, it's not feasible to fail an ingestion job because of a single error.

Lookout for Equipment operates with a bias toward complete ingestion. In other words, when it encounters a problem in the ingested data, Lookout for Equipment attempts to fix that problem automatically. Then it alerts you to whatever issues it encountered, and lets you know what fixes it implemented.

If your entire job fails, consider the following possibilities:

  1. The files are not .csv files, or they are corrupted, or they are unreadable for some other reason.

  2. The files were not named or organized as explained under Adding your data.

  3. The files contain no data, or 100% of the data they contain is not formatted in a way that Lookout for Equipment recognizes.

If your ingestion job fails, check the issues above and make the appropriate adjustments. When you’re ready to try again, go back to Adding your dataset.

Important

This page is about troubleshooting the ingestion of an entire job. You can also read about why some specific files don't get ingested, and about evaluating the data from specific sensors.

Checking the logs

If you enabled CloudWatch Logs, then the logs may help you troubleshoot ingestion issues. The published logs may include the following error codes:

  • COMPLETE_SENSOR_DATA_MISSING : A sensor has no valid data assosicated with it. The log contains the sensor name and the associated component name.

  • DATA_MISSING_IN_COLUMN : Data associated with a sensor is invalid at a particular timestamp. Along with the sensor name and associated component name, the log contains details about the timestamp and the associated file path.

  • UNSUPPORTED_DATE_FORMATS : A value in the timestamp column is invalid. The log contains details about the timestamp string, the path of the file, and the associated component name.

  • INSUFFICIENT_SENSOR_DATA : A sensor is associated with less than 14 days of data. The log contains the sensor name, the component name, and the date range of data (in days) associated with the sensor.

  • DUPLICATE_TIMESTAMPS : A value in the timestamp column of the data is a duplicate entry. The timestamp in question and the associated file path are part of the log.

  • FILES_NOT_INGESTED : A file was not ingested during the ingestion workflow. The log contains details about the file's path.