Auto-tools/Projects/Structured Logging: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
This page is a high level account of the structured logging project providing links to many resources about the project. This page is a work in progress.
This page is a high level account of the structured logging project providing links to many resources about the project. The readthedocs documentation should be consulted for up to date documenation of the mozlog api.


== Background and Motivation ==
== Background and Motivation ==
Line 30: Line 30:


* An [https://etherpad.mozilla.org/logging-status etherpad] with high-level status updates per test harness is maintained for the time being.
* An [https://etherpad.mozilla.org/logging-status etherpad] with high-level status updates per test harness is maintained for the time being.
== Structured Logging FAQ ==
* I'm not seeing the output I expect, what gives?
** Output for common use cases should be no less informative than it once was. You may have encountered an unintended effect of the implementation that should be addressed.
* How can I change the format of log output?
** For test harnesses logging through mozlog and their respective mach targets, you can pass in commandline arguments of the form "--log-<format>=<file>". Common formats are "mach", a concise format intended to be readable, "raw", the JSON structured format intended for post-processing, and "tbpl", a format designed to maintain compatibility with legacy tools hand-parsing our logs.
* Can't I just log "TEST-UNEXPECTED-FAIL"?
** If you have been relying on logging the string "TEST-UNEXPECTED-FAIL" directly to provide test coverage, this will do what you expect for the time being, but future support may be diminished.
Confirmed users
64

edits

Navigation menu