I create a custom ActivityLog that tracks user activity within my app and a custom HistoryLog that tracks data changes of any models.
For instance, when a user named Adam is updating a product in Tyre module:
Reason for having 2 seperate log modules is to track user activity and record of data changes.
My question is is this viable? How would this affect performance and server?
For context my client will deploy this first on shared hosting which I will advise him to deploy or Digital Ocean once user traffic reaches certain threshold.
Yes, it affects a little, since you need to make additional queries, but probably not so much that it's noticeable. As for shared hosting, it's not the best idea unless you have the correct document root from the host, or at have the possibility to change it.
I would host it on a dedicated server instead, and you can get those from the cloud provider of your choice.
@Tray2 i think @mkfizi-29935843 is storing record into log file not in the DB.
@amitsolanki24_ Could be, but the DB would be easier to find the changes.
@mkfizi-29935843 you can also check this activity log package
https://github.com/spatie/laravel-activitylog
I believe this is not a big deal. We can utilise the events and queue systems. To be more specific, eloquent events and queued listeners.
In my company, we are monitoring using New Relic with this mechanism. And I believe Laravel Pulse is doing the same.
Please or to participate in this conversation.
