-
Story
-
Resolution: Done
-
Medium
-
Dublin Release
-
None
-
None
-
El Alto Sprint 3
i. Add logging infrastructure.
a. Select a well known Node module to use as logger.
See: https://github.com/i0natan/nodebestpractices/blob/master/sections/errorhandling/usematurelogger.md for Node libraries to use as loggers
b. Define a set of log patterns to use (e.g. log line should have timestamp, transaction-id, log level, class name, etc..)
c. Define a set of rules for rolling-over log files (i.e. what is the max size of log file? should we keep a max number of log files on disk? should we archive older log files? should we rollover based on timestamp?)
ii. Log request-response between Loopback server and controller/processor mS
a. Capture HTTP request URI, headers (exclude Auth headers)
b. Capture corresponding HTTP response status code, headers
iii. Log request-response into Loopback server
a. Capture HTTP request URI, headers (exclude Auth headers)
b. Capture corresponding HTTP response status code, headers
1.
|
Add Logging Infrastructure | Closed | ramy1313 | |
2.
|
Log request-response between Loopback server and controller/processor mS | Closed | nirvan.ramjuttun | |
3.
|
Log request-response into Loopback server | Closed | ramy1313 |