From the event lists (Failure, Anomalies, Operation), you can export and import event definitions through CSV files.
This makes it easy to define events in bulk, review them offline, or replicate them across Thing Definitions and environments.
Both events and their remedies can be exported and imported.
Before importing, we recommend exporting the current definitions first. The exported file shows you the exact CSV format expected by the import.
Exporting Events or Remedies
To export events, you should:
Enter the event list and select the Thing Definition to export.
Press the Export button.
In the dialog, choose what to export:
Event Definitions: the definitions of events.
Remedies: the remedies associated with the events.
Confirm to download the CSV file.
The export includes only the events or remedies defined in the current Thing Definition.
If the Thing Definition inherits from a Super Thing Definition, the events and remedies inherited from it are excluded from the export.
Importing Events
To import events, you should:
Enter the event list and select the Thing Definition to update.
Press the Import button.
Select the CSV file with event definitions to import.
The system reads the CSV header and automatically detects whether the file contains event definitions.
Events are matched by Name:
If no event with the same name exists, a new event is created.
If an event with the same name exists, it is updated with the values in the CSV.
The import never deletes configuration elements. Events that already exist in the Thing Definition but are not present in the CSV are left unchanged.
Importing Remedies
To import events, you should:
Enter the event list and select the Thing Definition to update.
Press the Import button.
Select the CSV file with event remedies to import.
The system reads the CSV header and automatically detects whether the file contains remedies.
Remedies are linked to events through the event name in the CSV.
For each event referenced in the file, the system replaces the existing remedies with those in the CSV.
The import never deletes configuration elements. Remedies that already exist in the Thing Definition but are not present in the CSV are left unchanged.