Logging machine data in the Alarms data category (previously a separate app called Alarm Analysis) 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.

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 Alarms tab.
7. Click onAdd alarm 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. Alarms with an invalid configuration are not saved, indicated by . Alarms with a valid configuration are saved automatically.

   Field	Description
   Variable	Select the variable you want to track. Only variables with data type boolean or integer are available for alarms. 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 alarm.
   Type	Select the alarm type (details below). Option Description boolean (only available for boolean variables) This interprets the selected variable as a boolean. Value 1 (TRUE) will interpret the alarm as being active, while value 0 (FALSE) will interpret the value as being not active. This cannot be configured. If the logic in your machine is reversed, we'd love to hear from you. Please let us know by submitting your feedback at roadmap.ixon.cloud. value (only available for integer variables) This interprets the selected variable as a numerical value, where each value indicates a separate alarm. A lookup table will automatically open where you can define alarm details (details below). bit (only available for integer variables) This interprets the selected variable as individual bits, where each bit indicates a separate alarm. A lookup table will automatically open where you can define alarm details (details below). Value 1 (TRUE) will interpret the alarm as being active, while value 0 (FALSE) will interpret the value as being not active. This cannot be configured. If the logic in your machine is reversed, we'd love to hear from you. Please let us know by submitting your feedback at roadmap.ixon.cloud.
   Severity	This indicates how severe an alarm is. For value and bit alarm types, this field is not editable and instead needs to be configured in the lookup table (details below).
   Description	The description enables you to add more information or context to an alarm. For value and bit alarm types, this field is not editable and instead needs to be configured in the lookup table (details below).

8. If you selected an integer variable, the Lookup table will automatically open. The lookup table is used to translate the alarm values or bits, whichever relevant, into human readable alarms (e.g. Vacuum suction failure or Tape roll depleted). The default entry (name, severity, and description) will be used for every alarm that is not explicitly defined in the lookup table. Click onAdd value orAdd bit, whichever relevant, and enter the requested information for each value you wish to translate (details below). Entries with an invalid configuration are not saved, indicated by . Entries with valid configuration are saved automatically.

   Field	Description
   Value / Bit	Enter the value or bit, whichever relevant, you'd like to translate. This field is automatically filled, but can be freely changed. The default entry (name, severity, and description) will be used for every alarm that is not explicitly defined in the lookup table.
   Name	Enter the name of the alarm. This will be displayed in both components. The name of the default entry cannot be changed and will dynamically include the alarm value or bit, whichever relevant.
   Severity	This indicates how severe an alarm is and is displayed in both components.
   Description	The description enables you to add more information or context to an alarm and is only displayed in the Alarm history component.

9. Repeat the previous steps for each alarm you'd like to track.
   • Switching from Table to  CSV view enables you to more easily add alarms at scale. It is recommended to create at least one alarm in the table view first, and then switch to the CSV view to see what it looks like in a CSV format. Note that the default lookup table entry is not visible in the CSV view.
   • Additionally, once you've added them all once, the asset library makes it easy to add them to another asset.

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.

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

From now on, changes in the alarms are logged to IXON Cloud. No initial value is logged. Meaning the next value change will be the first value that is logged.

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