Adding detailed logging to hydrus

I’m submitting a

• bug report.
• feature request.

Current Behaviour:

Currently, we don’t have any detailed logging system for hydrus. No logs are being generated.

Expected Behaviour:

We can generate the log files which could help the users for getting the Object_id for any future manipulation and developers for debugging faster.

We will have a separate log folder that will be generated while running hydrus server.

Logs
|
|_ _ hydrus.log

Log file format

Logs/hydrus.log

run_time : 12-may-12:00:00
API_Doc fetched Successfully.
Context generated.
Terminated!
Database setup Error.

Do you want to work on this issue?

yes, I and @farazkhanfk7 are working on this and changing the API response structure issue .

[Mec-iS]

first of all we need to establish an id for each request and assign the request an unique id (like a uuid). you can do this by using the before_request and after_request; this should be present in each log line together with timestamp and HTTP method used and uri.

note: be sure that the log level is read from an environment variable and not hard-coded.

EDIT: you can start from structlog examples

please @farazkhanfk7 contribute to the discussion

[Mec-iS]

If you need a reference for logging, please check structlog. We may want to use it organisation-wide.

It has the same API as standard Python logging, but allows many more features and having much more structured logs.