Key considerations for migrating event data to BMC Helix Operations Management
Use the event migration utility to migrate data such as the Cell Knowledge Base (KB) rules along with the event classes and event data. This topic provides information about the data that you can migrate by using this utility and the event class mapping between TrueSight Operations Management and BMC Helix Operations Management.
For information about all the event slots in BMC Helix Operations Management, see Event classification and formatting.
Data that you can migrate
The following data is migrated when you migrate event data from TrueSight Operations Management to BMC Helix Operations Management:
- Event classes and slots
- Event rules
- Event policies
Notes about event policy migration
- If an event policy is configured for multiple event classes in TrueSight Operations Management, the event policy is migrated as multiple policies in BMC Helix Operations Management.
- If an event policy uses time frames in TrueSight Operations Management, the time frames are migrated to BMC Helix Operations Management. However, the following time frame configurations are not supported in BMC Helix Operations Management:
- Date list
- Duration
- Particular day of the month
- Yearly occurrence
If an event policy contains the above configurations in TrueSight Operations Management, the policy is created in the ALWAYS ACTIVE status in BMC Helix Operations Management. The policy description displays an error message for time frames. This is expected behavior.
Event class migration and mapping
In the event migration utility, event classes are categorized in the following types:
- Internal: This event class type is mapped to the out-of-the-box event classes in BMC Helix Operations Management, such as EVENT, PATROL_EV, or ALARM.
- Internal Third Party: This event class is defined for third-party event ingestion. If you create this class in BMC Helix Operations Management the third-party source also needs to use the BMC Helix Operations Management API for the event to be ingested. For example, Adapter Events, Log Events, and so on.
- Internal Deprecated: This event class type is not required in BMC Helix Operations Management.
- Custom: This is an event class type that you have defined in the TrueSight Operations Management Cell and is not a part of the out-of-the-box TrueSight Operations Management Cell.
Can I migrate the Internal Deprecated event class type?
Yes. To know how, see Installing and running the event migration utility.
The names of some event classes are different in TrueSight Operations Management and BMC Helix Operations Management. The following table displays the event class mapping between TrueSight Operations Management and BMC Helix Operations Management:
Points to consider
- While migrating a class, make sure that you select the class parent. If a class is already migrated, this selection is not required.
- If you want to migrate a custom class that is already migrated, make sure that you first delete the migrated custom class from BMC Helix Operations Management.
Event slot migration and mapping
A few TrueSight Operations Management slots are renamed in BMC Helix Operations Management. To understand this mapping, see the <migration_utility_download_directory>conf\tsomtobhomnamemapping.properties file.
A few TrueSight Operations Management slots are no longer used as child classes of the out-of-the-box BMC Helix Operations Management slots. If an event policy uses such slots, the policy is not migrated. To migrate such policies, perform the following steps:
- Open the <migration_utility_download_directory>conf\ClassSlots.csv file and delete the slot.
- Reload the event migration utility application and migrate the class again.
- Migrate the policy or rule that uses the slot.