Import Historical Sensor and Metric Data for Machines
If you have your pre-deployment device data in an external system, you can choose to import historical sensor and metric data into Oracle IoT Production Monitoring Cloud Service and use the data to train your analytics artifacts, such as anomalies and predictions.
Importing historical data is useful for cold start scenarios where you don't have training data already available in Oracle IoT Production Monitoring Cloud Service. You can also import data for proof-of-concept demonstrations, so that you can use the imported data to train your anomalies, predictions, and trends.
Note:
Pattern anomalies do not support imported historical data. To create pattern anomalies, you must generate training data in Oracle IoT Production Monitoring Cloud Service.Use the following steps to import historical sensor and metric data into Oracle IoT Production Monitoring Cloud Service:
- In Oracle IoT Production Monitoring Cloud Service, create and export a machine data template for your machine's data.
- Populate the machine data template with sensor and metric data from the external system.
- Import the machine data into Oracle IoT Production Monitoring Cloud Service. The data is available for training after validation and processing.
Export the Machine Data Template
The machine data template defines the schema for your machine data import. It includes fields for machine names and IDs, timestamps, sensor attributes, and metrics.