Skip to main content

Migration Execution Statistics report in Syniti ADMM Migrate

Syniti Knowledge PlatformMigrate

We need a migration execution statistics report. Below is the format of the report which will give execution statistics of a data migration object.

KPI report should look like below

Purpose: This report will give overall effort and time spent on an object.

Project

Release

Dataset name

Subject area

Execution date

ETL tasks

Run time in seconds

Records processed

Status

BBM

BBM_WB

open po

S2P

06 10:00

ekko

25

21312

ok

open po

06 10:00

ekpo

30

213123

ok

Posted by Arun Sasi Maliyakkal ·
6 comments

Log in to comment and vote

Comments6

  • jay.hornback@syniti.com

    •

    Aug 14

    @Arun Sasi Maliyakkal i have a query that looks at the “MIG” tables to get some, if not all, of the requirements you’ve posted. Please reach out to me, and I can show you how to add it and register it as a custom system report.

  • Kevin McDonald

    Team•

    May 5

    Hi Arunsasi - Thank you for your feedback — we’ve received it and are actively reviewing it.

    Should we need any additional details or clarification, we’ll reach out. We appreciate you taking the time to share your experience and help us improve the product.

    • Arun Sasi Maliyakkal

      •

      May 6

      Thanks @Kevin McDonald Let us know if there are any additional inputs required.

      Jon Green has been supporting us for this request. Below is the excerpt from his last email.

      Excerpt:

      The additional information in the ETL Jobs page / report, this will need to be treated as a feature request or be handled by Services in the short term.  I discussed with Migrate product manager regarding the feasibility of building out the required report as specified by Bosch, and it's not straight forward due to the transitory nature of the Job Queue details.  

      The Job Queue is parsed on a tenant specified cycle, deleting old logs so as to maintain performance of the job queue and the UI for investigating the Job Queue execution steps.  We store the latest execution statistics against the ETL Jobs but showing each previous run would involves putting in place a historical status capture process and adding a new MIG View to support the extraction of the job queue details.

      We haven’t seen this request at any other clients so at present we would need a feature request raised and then we will review the prioritization against the other requests that we have for review

      • Arun Sasi Maliyakkal

        •

        Jun 22

        Hi @Kevin McDonald

        Greetings for the day!

        Any update on this idea.

        • Kevin McDonald

          Team•

          Jun 23

          Hi Arun -

          It looks like this item is still in the Migrate Backlog, and has not yet been picked for development.

          • Arun Sasi Maliyakkal

            •

            Jul 16

            Thanks for the reply @Kevin McDonald Appreciate your response! Kindly update once this is picked up for Dev.