Administering Reports › About Reporting › Data Collection Process

Data Collection Process

Orchestrators collect and insert relevant information into the reporting database that is configured for the corresponding domain.

To avoid potential database-related performance degradation resulting from the execution of reports, the reporting database is isolated from the execution database that the Orchestrator use.

Similarly, the collection or reporting data is decoupled from its insertion in the reporting database:

• Orchestrators collect reporting data in staging tables of the main database when the data changes as a result of:
  • Configuration Changes
  • Modifications to the Library, such as creation of automation objects, check-ins of new/modified versions.
  • Execution of processes and operators.

If the reporting database is inline, Orchestrators periodically propagate batches of data from the main database to the reporting database. If there is a failure (such as, reporting database not available), the transfer is retried later.

As a result of the two-step process, there is a lag time between actions that Orchestrators take and the corresponding data being inserted in the reporting database. In normal situations, the delay is a couple of minutes.