Fixed
Details
Assignee
Dai HaDai HaReporter
Christopher ZimmermannChristopher ZimmermannPriority
MajorFix versions
Story Points
8Sprint
None
Details
Details
Assignee
Dai Ha
Dai HaReporter
Christopher Zimmermann
Christopher ZimmermannPriority
Fix versions
Story Points
8
Sprint
None
More fields
More fields
More fields
Created October 21, 2019 at 3:12 PM
Updated February 19, 2020 at 7:05 AM
Resolved January 22, 2020 at 7:53 AM
Currently, if a REST call fails a developer has no information about the REST call, and does not even necessarily know if it failed.
It's tricky for a developer because the problem could be in many places: in the restclient definition, or it could be with the external service itself, or it could be in the FTL or in the App configuration. Its easy to introduce a problem in the call since the calls themselves are often dynamically constructed.
Acceptance Criteria:
An error while making a REST call should be written to the log.
Dedicated log file?
All details about the request and response should be included - body, cookies, headers, parameters.
Secure information should not be written to the log.
Additional ideas for later:
Secure info is only written when the server is in developer mode.
If call can be written in a format compatible with 'curl' that is a bonus, because then developers could try it.