Open dandv opened 10 years ago
I have been thinking about better log message filtering facilities in Trail recently. I'm planning to improve it soon. Suggestions like these are very much appreciated. I'll update my GitHub settings to send emails to my primary mail account, so I will respond more quickly in the future.
Namespacing is already partially implemented using tags, but many simple improvements are possible.
Dynamically changing log level and even filtering options sounds like a very useful feature. I have to think about how to fit that in with Trail exactly. But I definitely want this feature now.
Could you edit the Meteor.settings object at runtime? Does it check that only once when things spin up, or each time a log message is created?
I think I saw a node logging module that had this feature - change the log level at runtime, for given methods even, to delve into problematic areas. pince implements namespacing and dynamic log level change on the client, but not on the server.