Manta Statistics API

Manta Statistics API can predict the duration of a workflow execution, even the expected duration of a single scenario.

Description

IBM Automatic Data Lineage uses scenarios as instructions to execute actions — each supported technology has defined scenarios, usually categorized as extraction, analysis, and export. For example, Oracle defines the Oracle Extractor Scenario and Oracle PLSQL Dataflow Scenario that relate to the extraction and analysis phases. To define more complex actions, Automatic Data Lineage allows you to create workflows in Process Manager. For more detailed information, see Manta Process Manager.

Each scenario needs to be run with a specific connection and behaves differently based on the data stored in the remote system (defined by the connection). Automatic Data Lineage can predict the duration of each scenario based on past executions of the workflows.

Prerequisites

To see relevant statistics, you’ll need:

1. A workflow definition

2. At least one successfully completed execution of the workflow (more executions make the statistics more precise)

Only successful executions are used to calculate the statistics.

Usage

As described in Manta Orchestration API, navigate to Swagger, find the section Workflow Statistics, and follow the API documentation.

Responses

{
  "averageSeconds": 93,
  "workflowExecutionSteps": [
    {
      "scenarioName": "diagnoseRepositoryScenario",
      "connectionName": "",
      "averageSeconds": 26
    },
    {
      "scenarioName": "oracleDictionaryMappingScenario",
      "connectionName": "oracle",
      "averageSeconds": 4
    },
    {
      "scenarioName": "oracleExtractorScenario",
      "connectionName": "oracle",
      "averageSeconds": 5
    },
    {
      "scenarioName": "newRevisionScenario",
      "connectionName": "",
      "averageSeconds": 3
    },
    {
      "scenarioName": "oracleDdlDataflowScenario",
      "connectionName": "oracle",
      "averageSeconds": 7
    },
    {
      "scenarioName": "oraclePlsqlDataflowScenario",
      "connectionName": "oracle",
      "averageSeconds": 7
    },
    {
      "scenarioName": "oracleDictionaryDataflowScenario",
      "connectionName": "oracle",
      "averageSeconds": 6
    },
    {
      "scenarioName": "repositoryPostprocessingScenario",
      "connectionName": "",
      "averageSeconds": 4
    },
    {
      "scenarioName": "interpolationDataflowScenario",
      "connectionName": "logical",
      "averageSeconds": 5
    },
    {
      "scenarioName": "interpolationDataflowScenario",
      "connectionName": "business",
      "averageSeconds": 5
    },
    {
      "scenarioName": "collectStatisticsScenario",
      "connectionName": "",
      "averageSeconds": 6
    },
    {
      "scenarioName": "commitRevisionScenario",
      "connectionName": "",
      "averageSeconds": 3
    },
    {
      "scenarioName": "pruneRevisionScenario",
      "connectionName": "",
      "averageSeconds": 4
    }
  ]
}

The response defines the expected seconds count for the whole workflow and for each scenario in the workflow. The expected times are calculated as the average of the last three runs.

The statistics reset whenever the workflow has been changed and executed at least once since the change.