Connector Scheduling - Best Practices

Connector Frequency

When setting up the Oomnitza connector on your end, it's important to consider how often it runs. The Oomnitza connector is built to asynchronously process large quantities of information and parse them into a usable format.

The connector essentially works in three steps:

  1. Data is pulled from the third party system (e.g. Jamf, Airwatch, Okta).
  2. Data is translated into an Oomnitza-compatible format.
  3. Transformed data is sent to Oomnitza and used to update the appropriate assets.

Depending on the volume of the data being processed, this process can take anywhere from a few minutes to a few dozen minutes.

When large volumes of data are being processed, it's important to be aware of when your connectors are running, in order to decrease the load your Oomnitza system. While Oomnitza monitors systems and provides more resources as necessary, it's still possible that an over-active connector can cause performance issues.

To avoid that, we recommend you follow these rules when configuring your connectors:

  1. When running multiple connectors, don't launch them in parallel. If possible, time connectors so one runs after the other finishes. This ensures that system resources process data as it comes in, without creating a backlog of data to parse.
  2. Run your connectors as infrequently as possible while allowing necessary data pull. While you may be inclined to run connectors as frequently as possible, the connector is designed to run asynchronously and should be used sparingly. We recommend a maximum frequency of every 2 hours.

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


Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk