Comments (3)
Hi Wolfgang,
winston is a necessary dependency of this library, since it provides the logging level logic and output transport system.
Using the library without express (or restify) should be possible, but will be limited to custom logs. If this your intention, we can provide an example soon.
If you want to log network activity from any other module than express or restify, it is necessary to implement and bind another specialized logger (like log-express and log-restify), which extracts request data.
Kind regards,
Christian
from cf-nodejs-logging-support.
Hi Christian,
thanks for the feedback; yes an example without express would be great.
Second, and along the line of what you call custom logs (in the sibling java project we distinguish between request logs and app logs): wouldn't it be also possible to create a request log "by hand", i.e. providing the relevant fields such as response time as explicit part of the log creation?
Cheers, Wolfgang
from cf-nodejs-logging-support.
Hi Wolfgang,
we have just implemented logging support for node.js http module, which is part of node.js. That includes request and custom logs. You can find an example in the documentation.
Writing request logs by hand is possible, but our take on this library was to provide a clear and distinct api, and to make sure that every written log matches the logging schema.
Kind regards,
Christian
from cf-nodejs-logging-support.
Related Issues (20)
- Array with stacktrace is stringified and resulting JSON is incorrect HOT 3
- Removing unnecessary logs HOT 3
- Avoid publishing dev folders like docs & tools HOT 5
- Mend reports for jsonwebtoken-8.5.1 please consider upgrade jsonwebtoken to ^9.0.0 HOT 1
- Possible vulnerability due to missing JWT public key type check
- logMessage is not using the customFields in v7 HOT 2
- CorrelationId not set when creating Child Logger HOT 4
- Fastify support HOT 15
- Winston Support in v7 HOT 3
- Log layer field is always [NODEJS] HOT 7
- custom fields are not logged correctly for request logger HOT 1
- cf-nodejs-logging-support and @sap/logging HOT 4
- using req. context logger in qunit test with nock
- tenant_id still missing in the request logger HOT 3
- ReferenceError: defaultConfig is not defined HOT 1
- Switch off the INFO log on KIBANA HOT 1
- Switch logLevel HOT 3
- Clear (my) confusion: cf-nodejs-logging-support vs @sap/logging HOT 7
- Logs contain incorrect url in "request" field HOT 2
- Extraction of logging level fails with window object HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cf-nodejs-logging-support.