I would like to store or record the users activities like when login, logout or insert, updates, remove data with datetime, docs info, user id fields …
You could use collection-hooks for this ( https://github.com/matb33/meteor-collection-hooks )
You could then create a function that takes a collection as argument and automatically binds the correct hooks to the collection.
So you could have something
var Foo = new Mongo.Collection(“foo”);
This package does something similar to partition collections: https://github.com/mizzao/meteor-partitioner
Thanks, look great for the collection hook package, but I don’t understand how to record action. It mean that I should store info in mongo collection? ???
Well, you can attach hooks/listeners before and/or after any insert/update/remove/read from a collection. So in such a hook you can log that action to your mongodb, log file or other system of your choice.
For performance reasons I wouldn’t save it to your mongodb of meteor, as it will add data to the oplog, which meteor has to process but which you probably don’t expose in any publication (I assume)
what the oplog?
Meteor hooks into the mongodb oplog (operation log to keep mongodb instances synchronized) in order to receive updates form the db to act upon.
Everything that will get inserted into the mongodb instance used by meteor will be added to the oplog and therefore processed by meteor (to see if it matches any publication). If you have data that is never going to be exposed by a meteor publication, it might be better (performance-wise) to store that in a separate database.
Thanks, but I don’t understand and I will try store on collection of mongodb.
But where do you want to store this info if not into mongodb?
This kind of auditing would be very valuable (especially to track changes to the collections) for security purposes.
Perhaps the collections packages should have meta collection to auto-magically take care of these (security audits)
Oh, look great if have this package (security audits).
“But where do you want to store this info if not into mongodb?” – vicusbass
How about Redis? Then periodically dump into MongoDB for persistence.
p.s. Hope you don’t mind me resurrecting this question, but have similar concerns in mind.
Maybe this can be interesting: https://www.compose.io/articles/redis-mongodb-and-the-power-of-incremency/