Uploaded image for project: 'Okapi'
  1. Okapi
  2. OKAPI-1072

Additional tracing info of module activation

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • TBD
    • Resolution: Done
    • None
    • 4.13.0
    • None
    • CP: sprint 133
    • 1
    • Core: Platform
    • TBD

    Description

      In scope of UXPROD-3387 we need to measure time of module activation for the tenant. The thing is that to leverage okapi dependency management capabilities we have to make a single request to okapi with all of the modules we want to activate for the tenant. Obviously in such case the only parameter we can measure is overall activation time. In case of to o long activation we need to identify which exactly module migration took most of the time. So, OKAPI and services itself are the components which know how much time this activation took.

      In scope of this task we want to add additional INFO messages to OKAPI log related to this activation process timeline measurement in the following format:

      • Starting activation of module '${moduleName}' for tenant '${tenant}'
      • Activation of module '${moduleName}' for tenant '${tenant}' successfully completed in ${period} seconds
      • Activation of module '${moduleName}' for tenant '${tenant}' failed

       

       

       

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                adam Adam Dickmeiss
                Vitaly_Demchenko@epam.com Vitaly Demchenko
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases