Key considerations for migrating event data to BMC Helix Operations Management
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 rules
- Event classes and slots
- Event policies
Important
- You cannot migrate rules that contain deprecated event classes. If a rule contains deprecated event classes, an error is displayed during the 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.
Change the class type to INTERNAL_THIRD_PARTY for the migration. To know how, see Installing-and-running-the-event-migration-utility. - 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.
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.
Migrating precedence with event policies or rules
Use the event migration utility to migrate event polices or rules along with their precedence. By migrating the precedence number, you do not have to add the precedence manually to the migrated polices in BMC Helix Operations Management.
Scenario
Sarah is a tenant administrator in Apex Global. Her company has moved from TrueSight Operations Management to the SaaS-based BMC Helix Operations Management for their monitoring needs. After migrating polices from TrueSight Operations Management to BMC Helix Operations Management, she realizes that she needs to manually add the precedence number in BMC Helix Operations Management.
Can Sarah avoid this manual task when she runs the migration utility again?
Yes. She can add the precedence order of policies when she runs the migration utility.
When a policy or rule is migrated from TrueSight Operations Management to BMC Helix Operations Management, the following factors are taken into consideration:
- The rule execution order in the kb/rules/<rulefilename>.mrl file
- Cell start and end indexes
During migration, the policy precedence number is allocated within the range that you specify for the KB cells. Spacing between rules or policies
You can specify 2 to 5 spaces between policies. With this setting, you reserve spaces for precedence numbers between migrated policies. After migration, if you create new policies in BMC Helix Operations Management, you can place the precedence numbers in the reserved spaces between the migrated policies.Scenario
As a tenant manager in Apex Global, Sarah has migrated policies A, B, and C from TrueSight Operations Management to BMC Helix Operations Management. The precedence numbers of the policies are as follows:
Now Sarah needs to create policy A1 in BMC Helix Operations Management with the precedence number 6. Luckily, because of the spacing that she used while migrating polices A, B, and C, she can go ahead and create policy A1 without editing any of the migrated polices for the precedence number.
The precedence order of rules and policies in TrueSight Operations Management
The following table displays the precedence order: