Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-48702

Improve course log export resource consumption and reliability (backport of MDL-34867)

XMLWordPrintable

    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • Hide
      1. Run the unit tests in:
        1. admin/tool/log/store/standard/tests/store_test.php; and
        2. admin/tool/log/store/legacy/tests/store_test.php
      1. Navigate to Site administration > Reports > Logs and select “Standard log” from the dropdown
      2. Click “Get these logs” (If that option is not available then you are already viewing the standard log by default.)
      3. Check that you can view log data.
      4. Re-enable legacy logging (You can enable legacy logging from Site administration > Plugins > Logging > Manage log stores. Select the option "Log legacy data" and save changes).
        Note: Since M27, log data is no longer stored in the table mdl_log by default but we will need some data generated in order to verify the downloaded data.
      5. From the Logs page select the “Legacy log” option from the dropdown and select “Get these logs"
      6. Check you can view log data
      Show
      Run the unit tests in: admin/tool/log/store/standard/tests/store_test.php; and admin/tool/log/store/legacy/tests/store_test.php Navigate to Site administration > Reports > Logs and select “Standard log” from the dropdown Click “Get these logs” (If that option is not available then you are already viewing the standard log by default.) Check that you can view log data. Re-enable legacy logging (You can enable legacy logging from Site administration > Plugins > Logging > Manage log stores. Select the option "Log legacy data" and save changes). Note: Since M27, log data is no longer stored in the table mdl_log by default but we will need some data generated in order to verify the downloaded data. From the Logs page select the “Legacy log” option from the dropdown and select “Get these logs" Check you can view log data

      See MDLSITE-3683. If you have a lot of data logged you can easily start running into memory allocation errors when you start retrieving log data. The calling code can cap the number of records it asks for but this is far from ideal if you are trying to aggregate log data.

            andyjdavis Andrew Davis
            andyjdavis Andrew Davis
            Dan Poltawski Dan Poltawski
            Dan Poltawski Dan Poltawski
            Dave Cooper Dave Cooper
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.