frm
Well-known member
Right now, XenForo has a Server error log and E-mail bounce log.
I would propose other log types such as a Cron execution log; a Custom field change log would be nice (in addition to saving edit history), and while there is a Custom thread field log add on, it doesn't work for all custom fields across all add ons that could implement it; and the User Change log moved into the same format as Server error log and E-mail bounce log to catch spammers much easier.
A lot of add ons run cron jobs, and while they might not be recorded in the Server error log, they could not be doing the process as intended. It would be quite hard to figure out, without looking into it every once in a while, that a Cron job executed but didn't behave accordingly. If there was a Cron execution log, it could record what was executed and what it did for immediate further inspection.
Right now, I have Cron execution logs saved to the Server error log so I can see that it executed and then investigate whether it did anything as intended. But, the error log notice is quite annoying as I have to sift through it to make sure there aren't other critical errors.
Developers could add Cron execution logging so that if, for instance, there was a XF schema change and an add on was supposed to do something, but didn't, and didn't error out because there was no error to be sent, it would give admins a clearer picture on what to report so that it could be looked into and fixed.
I would propose other log types such as a Cron execution log; a Custom field change log would be nice (in addition to saving edit history), and while there is a Custom thread field log add on, it doesn't work for all custom fields across all add ons that could implement it; and the User Change log moved into the same format as Server error log and E-mail bounce log to catch spammers much easier.
A lot of add ons run cron jobs, and while they might not be recorded in the Server error log, they could not be doing the process as intended. It would be quite hard to figure out, without looking into it every once in a while, that a Cron job executed but didn't behave accordingly. If there was a Cron execution log, it could record what was executed and what it did for immediate further inspection.
Right now, I have Cron execution logs saved to the Server error log so I can see that it executed and then investigate whether it did anything as intended. But, the error log notice is quite annoying as I have to sift through it to make sure there aren't other critical errors.
Developers could add Cron execution logging so that if, for instance, there was a XF schema change and an add on was supposed to do something, but didn't, and didn't error out because there was no error to be sent, it would give admins a clearer picture on what to report so that it could be looked into and fixed.
Upvote
5
