Logging machine data in the Metrics data category (previously a separate app called Metrics) is part of the overarching feature Historical data logging.

Data categories are a built-in part of historical data logging and provide a way to log data in an organized manner, as explained in Categorize machine data with data categories.

For frequently asked questions, see Categorized machine data FAQ.

• Preparation
• Add log items

Preparation

Before you can start logging data, you will need to make some preparations.

1. If you haven't already, start in Historical data logging.
   • Data categories are only a part of this overarching feature. The main article contains relevant information, like required license(s) and preliminary steps.
2. If you currently have tags configured, make sure to read the Categorized machine data FAQ before you proceed.

3. Set up an asset and link a device to that asset.

   Data loss

   Be aware that if you unlink the device from the asset, that will automatically and immediately delete all previously logged data for all categorized log items on the asset and all its sub-assets. This cannot be undone. Once a device has been linked again and a correct configuration has been pushed to the edge gateway, it will start logging new data.

   For an overview of all actions that result in loss of data, see Categorized machine data FAQ.

Add log items

To log machine data, you'll need to add log items. Add a log item for every variable that you want to log. Note that you can create multiple log items for the same variable. Useful if you wish to log a variable's minimum and maximum value for example.

4. Go to Fleet Manager > Assets and click on your asset name.
5. In the asset tree, click on the (sub-)asset where you want to add log items.
   • If you have built an asset tree that represents your machine layout, it is recommended to organize your data per machine part or section. Select a (sub-)asset.
   • If you only have a single asset in your tree, simply select that asset.
6. Go to the Metrics tab.
7. Click onAdd metric and enter the requested information (details below). If you are unable to see this option, your asset may be an instance of a library asset and will need to be edited in the asset library instead.

   Field	Description
   Variable	Select the variable you want to track. If you are unable to see any variables, go to the General tab and make sure that your device is linked to your asset.
   Name	Enter a name for the metric.
   Identifier	The identifier is entered automatically and ensures that every metric remains unique, even if they share the same name.
   Log on	Interval Log data on a time interval. Custom allows any interval between 100ms - 1h (enter the value and unit, e.g. 500ms, 30s, or 5m). Change Log data when the value in the machine changes. Useful for values that don't change often. This also prevents logging the same consecutive values (e.g. true, true, true, etc.) and thus prevents clutter. The Statusbar component only shows a status up until the last logged value. If the value doesn't change often, this component may show a gap of data between the last value change and now. To bridge this gap and thus more accurately depict the machine status, a configuration option was added. This field is called Specification with the new option being On value changes and each hour of unchanged value. Requires SecureEdge / SecureEdge Pro firmware 5.0 or higher, IXrouter3 firmware 3.13 or higher, or IXagent version 0.4.3 or higher. Not supported on the Windows IXagent. Trigger Log data on a custom trigger. Useful to log data at machine-specific events. For example when a certain temperature has been exceeded, an error occurred, or when a product leaves a conveyor. Log triggers need to be configured separately. Follow the instructions and come back here once you have: Configure log triggers. Requires SecureEdge / SecureEdge Pro firmware 5.0 or higher, IXrouter3 firmware 3.11 or higher, or IXagent version 0.4.0 or higher.
   Formula (log on interval only)	The edge gateway will continuously request data from the machine, regardless of your logging interval. This enables you to log an aggregated value each interval, like the average value or the maximum value that occurred. Requires SecureEdge / SecureEdge Pro firmware 5.0 or higher, IXrouter3 firmware 3.7 or higher, IXrouter2 firmware 2.11 or higher, or IXagent version 0.4.0 or higher. Mean Logs the average value. Min Logs the minimum value. Max Logs the maximum value. Last (default) Logs the most recent value. Increase Logs the increase in value. Useful for production counters. All value decreases are ignored. For example, if the value changes from 0 to 5 to 0 to 5, the logged value is 10. Requires SecureEdge / SecureEdge Pro firmware 5.0 or higher or IXrouter3 firmware 3.21 or higher. More information and tips: Visualize production counters in IXON Cloud.
   Retention policy	Enter how long you want to store your data in the cloud. Requires your license/module to remain active.

8. Repeat the previous steps for each metric you'd like to track.
   • It is not possible to add metrics in bulk. However, once you've added them all once, it's much easier to add them to another asset by using the asset library.

You have now made the changes in the IXON Cloud, but these are not yet active in your device. You will need to push your changes to your device for them to take effect.

9. Click on Push config to device in the top right corner.

From now on, data will be logged based on how you configured your metrics. No initial value is logged. Meaning for metrics that are configured to log on change, the next value change will be the first value that is logged.

10. Click below to continue in the feature specific article.
    • Historical data logging