Migrate existing instrumentation


You store instrumentation in folders on the management server, ready for deployment to nodes. HPOM 8.00 introduced a different structure for instrumentation folders. However, after you upgrade from OVO 7.50 you could still have your own custom instrumentation in folders that follow the deprecated structure.

Note NOTE:
If you have not yet upgraded a Smart Plug-in (SPI), this could also have placed instrumentation in folders that follow the deprecated structure. However, when you upgrade the SPI it will automatically migrate its instrumentation to the new folder structure.

In OVO 7.50, the instrumentation folders have the following structure:
<data_dir>\shared\Instrumentation\<OS Name>\<OS Version>\<Category>

For example:
<data_dir>\shared\Instrumentation\Windows XP\5.1\ExampleCategory

In HPOM 8.10, the equivalent folder is:
<data_dir>\shared\Instrumentation\Categories\ExampleCategory\Windows\5.1

OVO 7.50 also creates the following default instrumentation categories:

In the HPOM 8.10 instrumentation folder structure, there is no equivalent of the Action, Command, and Monitor folders. You must create alternative categories.

HPOM 8.10 still supports the deprecated instrumentation folder structure for nodes that have a DCE agent:

If you have your own custom instrumentation in the deprecated folder structure, consider migrating it to the new folder structure. This is essential if you want to deploy the instrumentation to nodes that have an HTTPS agent.

To migrate existing instrumentation, create folders according to new folder structure, and move the instrumentation files into them. For more information on the new instrumentation folder structure, see Associate instrumentation with policies.

Related Topics: