You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fastify http event server used for observing events from stacks-core needs improved logging. Some logs we had when using Express also no longer show up.
Request completed log
The "request completed" log line isn't very useful by itself. It includes a randomly generated requestID that must be matched against a previous log entry to get the useful details url, request body size, etc.
Log an error/warning when the stacks-node submits an http request and then terminates the http connection before we have replied. Currently there aren't useful logs for when this happens.
The text was updated successfully, but these errors were encountered:
The fastify http event server used for observing events from stacks-core needs improved logging. Some logs we had when using Express also no longer show up.
Request completed log
The "request completed" log line isn't very useful by itself. It includes a randomly generated requestID that must be matched against a previous log entry to get the useful details url, request body size, etc.
Example of existing log line:
Unexpected connection termination logging
Log an error/warning when the stacks-node submits an http request and then terminates the http connection before we have replied. Currently there aren't useful logs for when this happens.
The text was updated successfully, but these errors were encountered: