Closed Bug 1442914 Opened 7 years ago Closed 7 years ago

Access logs should be in "mozlog" json schema

Categories

(Conduit :: Lando, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: smacleod, Assigned: smacleod)

References

Details

(Keywords: conduit-triaged)

Attachments

(2 files)

Lando currently logs its custom logging calls in "mozlog"[1] but log messages from flask are using the default format. Lando's logging should be updated so that the access logs that come from flask are in mozlog format. [1] https://wiki.mozilla.org/Firefox/Services/Logging
Blocks: 1443579
No longer blocks: 1441728
Keywords: conduit-triaged
Assignee: nobody → smacleod
The mozlogging package made it so our calls to `logging.<level>()` would have a strange signature, not following the standard convention of the `logging` module. This change introduces an updated logging formatter that expects `logging` calls to use the standard arguments. Logged messages now adhere to Dockerflow and each field in the log message is semantically correctly. The access logging messages have been updated to be Dockerflow compliant, using the 'request.summary' message schema. The pytest library has also been updated to allow for use of the `caplog` fixture going forward. This should make testing logging messages easier. Also, logging is no longer disabled during test runs, making test failures much easier to diagnose (pytest will write the logged messages out for the failed test).
Comment on attachment 8973824 [details] logging: make logging calls have conventional signatures (Bug 1442914). Byron Jones ‹:glob› has approved the revision. https://phabricator.services.mozilla.com/D1157
Attachment #8973824 - Flags: review+
The access logging messages have been updated to be Dockerflow compliant, using the `request.summary` message schema. As part of this Flask/Werkzeug access logging has been disabled, meaning all log messages should be mozlog. The mozlogging package made it so our calls to `logging.<level>()` would have a strange signature, not following the standard convention of the `logging` module. This change introduces an updated logging formatter that expects `logging` calls to use the standard arguments. Logged messages now adhere to Dockerflow and each field in the log message is semantically correctly. Logging is also no longer disabled during test runs, making test failures much easier to diagnose.
Comment on attachment 8976654 [details] logging: log all requests in mozlog format (1442914). Israel Madueme [:imadueme] has approved the revision. https://phabricator.services.mozilla.com/D1303
Attachment #8976654 - Flags: review+
This should now be fixed in both lando-api and lando-ui
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: