virtuatable-museum / virtuatable

Utility classes for the virtuatable services
0 stars 0 forks source link

Add better logging capacities #10

Open vincentcourtois opened 5 years ago

vincentcourtois commented 5 years ago

Current logs are only the API responses. Logs should be written in decicated files (debug.log, infos.log, errors.log) in a dedicated directory (might be a linked one), then served via a common GET /logs route defined in the Arkaan::Utils::Controllers::Checked class

vincentcourtois commented 5 years ago

test that errors are corretly logs in particular :

  1. there is a call triggering an error
  2. check status
  3. check body
  4. check the existence of a error.log file
  5. check the size of the file
  6. check the content of the file
vincentcourtois commented 5 years ago

Maybe for the common errors we should be able to display a more descriptive response body. Even if we do so, we should not display the error to everybody, and not give too much informations in the data field.