Details
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:
- Update the logs to validate these text/mediumtext data types for character length
- 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)
- Some places that may be appropriate are:
Issue Links
- relates to
-
CORE-2943 Replace serialization with JSON where possible
- Open
Issues in Epic
|
CORE-2957 | Automatically split log data stored for gateways and modules | Closed | Tyson Phillips |
CORE-2956
Truncate Stored Logs
false
CORE-2956
Truncate Stored Logs