Skip to content
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.

Latest commit

 

History

History
53 lines (35 loc) · 2.2 KB

20-Import-source.md

File metadata and controls

53 lines (35 loc) · 2.2 KB

Use iTop exports as an Import source

Hint: This chapter assumes that you are already familiar with the Icinga Director Import and Synchronization mechanism.

Add a new Import source

Given that, the next steps should be fairly easy. From the Import source overview, click Add import source and choose the iTop Export option for Source Type:

Add Import source

Select a iTop resource

With this selection, you specify from which iTop instance you want to export data from:

Select Resource

Initially, this list is empty. You have to provide a iTop resource in the resources.ini file usually located at /etc/icingaweb2/. There is currently no possibility to create such type of resource within the Icinga Web 2 interface. This means that the only way to do it for the moment is by modifying the resources.ini file manually. The iTop resource should look as follows:

[iTop_demo]
type = "iTop"
url = "http://demo.example.com/itop"
username = "user"
password = "pass"

Provide query or expression

In order to specify which data you want to export from iTop and import into Icinga, you have 2 options.

Select query from phrasebook

After you selected a iTop resource, the module retrieved a list of queries from the iTop Query phrasebook of the selected resource. Select one of the available queries and that's it.

Provide custom OQL query

If you select Custom… from the list of queries, you will be able to provide a custom OQL query. Please see the iTop documentation on how to do that. You will also need to provide the fields needed for the import/export:

Provide Expression Fields

Localisation

Last step is to select whether or not translation of the iTop enum values and field names should occur. This is mostly not the case, so selecting no for Localize will usually be sufficient.