filog
filog copied to clipboard
fgm
A fine logger package for Meteor.JS applications (client + server)
* Meteor 2 support. Dropped 1.x support. Node 14.* required. * No significant code changes * Major dependency updates * Node 12 → 14, NPM 6 → 7 * Many...
Introduce a SourceProcessor modifying the context handling logic to format context introduced by client processors within a `context.client` property, (resp. `server`, `cordova`), and introduce a top-level `source` property identifying the...
I have ended up customizing my fork of FiLog to have the option to limit the amount of exceptions that are logged by `logger.arm()`, by giving it as an argument...
The Beacon API allows sending data without waiting for the result, which is often what is expected from front-end logging, to minimize impact on user interactions.
Userland code is known to have added this, in order to be able to configure levels as strings in settings. Should probably ignore case and support spelling variations (e.g. emerg...
The 0.1.x README targets both devs considering using the logger and devs actually engaged in developing with it. And fails both, being too complex for the former and insufficient for...
I'm wondering, is it intentional to include app source code in the log messages? ```JSON { "_id": "eLnvfTgZhHDZtLWQ6", "level": 3, "message": "t.target.closest is not a function", "context": { "message_details": {...
I have been using FiLog with a custom sender when in development mode, "DevSender", which will log to the console, but only produces one line per log event. This way...
MongoDB sender seems to be losing information on the logged error on the way to the database. ### How to reproduce ```js // /server/index.js try { throw new Error('Oops!'); }...
In a distributed environment, which is quite frequent in Meteor apps, it is difficult to track the full path of a request. * Having correlation IDs (aka "tags") allows tracking...