php - Single centralized or separated log table for modules? -
I am preparing an intranet system for medium business. Should I put a single log table for all modules or separate it?
The audit log maintains all administrator / staff activities (create, update, delete objects) and log structure is universal for any type of module.
And this is also a good idea if I pull reports based on log records? My log table contains the object type and the object ID, so I can get data for any object and at any point of time, depending on the event, object name, and object ID.
What is the best way to report such cases?
Well, when you review your logs, what you want to do, look in one place Where can you see everything or examine many different places, each of which shows a piece in the isolation system?
Keep in mind that, with a table, it is trivial to filter those entries that are irrelevant or do not have authorization to view the user. By combining several personal logs into a single, comprehensive view, It is easy, as well as most of its design can cause additional damage, you need to repeat the code, which adds a new log table each time.
I definitely have to say that a log is better. The only situation I can think is that many different logs where appropriate if safety concerns should be strengthened so that log entries can be physically separated with different visibility - and, in such a case, you may be seeing separately Log server, not only separate tables.
Comments
Post a Comment