A single centralized or split log table for modules?

I am developing an intranet system for medium-sized businesses. Should I keep one log table for all modules or make it separate?

The audit log contains all the actions of the administrator / personnel (creating, updating, deleting objects), and the log structure is universal for any type of module.

And is it also good if I output a report based on journal entries? My log table stores the type of the object and the identifier of the object, so I can receive data for any object and at any time based on events, the name of the object and the identifier of the object.

What is the best reporting approach in such cases?

+3
source share
4

, , , , , ?

, , . , , , , , .

, . , , , , , , - , , , .

+2

. log4php. log4j , . , log4php, .

+3

.

, , ( ). .

. , .

, ( ). DROP CREATE, . , , objectid .

+3

, , . . , this.

+1

Source: https://habr.com/ru/post/1707142/


All Articles