Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2956

Split database logs to adhere to character limitations

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Gateways, Modules
    • Labels:
      None
    • Epic Name:
      Truncate Stored Logs

      Description

      In a number of locations, we store logs to the database, typically under "log_*" tables. However, some of these logs can handle a lot of characters (e.g. text, mediumtext types), and will lead to a database error if attempting to store too much information.

      We should:

      1. Update the logs to validate these text/mediumtext data types for character length
      2. Update existing logs that exceed the maximum character length to automatically split the logs into multiple logs where appropriate
        • Some places that may be appropriate are:
          • Email Logs (log_email)
          • Module Logs (log_module)
          • Gateway Logs (log_gateway)
          • Client Setting Logs (log_client_settings)
          • Contacts Log (log_contacts)
          • Cron Log (log_cron)
          • Transaction Log (log_transaction)

        Issue Links

          Issues in Epic

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                tyson Tyson Phillips (Inactive)
                Reporter:
                tyson Tyson Phillips (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: