Best practices for scheduling basic integrations

When you set up a basic integration locally, you must schedule the integration so that it doesn't adversely affect the performance of your system.

Basic integrations asynchronously process large volumes of data and parse the data into a usable format.

The three data-processing steps are:

1. The data is pulled from a third-party system such as Cisco.
2. The data is transformed so that it is compatible with and can be consumed by Oomnitza.
3. The transformed data is sent to Oomnitza and is used to add and update asset records.

Depending on the volume of data that is being processed, these processes can take a short time, a few seconds, or a long time. The length of time it takes to ingest the data depends on the volume of data that is being ingested and the consumption of system resources.

Although Ooomnitza monitors the running of basic integrations and provides additional resources when required, the processing of large volumes of data might impact the performance of your system.  

To prevent performance issues, adhere to the following best practices when you configure basic integrations:

• When you run multiple basic integrations, avoid scheduling the integrations to run at the same time. If possible, stagger the scheduling so one basic integration runs after the other basis integration has run. The data will be processed when it is received and backlogs of unparsed data won't be formed.
• Run basic integrations as infrequently as possible. While you might be inclined to run basic integrations as frequently as possible, basic integrations are designed to run asynchronously and should be run infrequently. A maximum frequency of every 2 hours should be sufficient.

Note
When hosting the Oomnitza basic integration, it's recommended that the VM be set to UTC to avoid confusion with timing between the basic integration and Oomnitza.