Auto-tools/Projects/Structured Logging: Difference between revisions
< Auto-tools | Projects
Jump to navigation
Jump to search
Chmanchester (talk | contribs) |
Chmanchester (talk | contribs) |
||
| Line 9: | Line 9: | ||
Approach: | Approach: | ||
* Establish a common data format for test results | * Establish a common data format for test results | ||
* Populate data format in-harness with a standardized logging API | * Populate data format in-harness with a standardized logging API | ||
* Log data from test harnesses as data structures rather than formatting them into strings | * Log data from test harnesses as data structures rather than formatting them into strings | ||
Revision as of 21:42, 24 August 2014
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.
Background and Motivation
Goals:
- Support a wider range of output formats
- Eliminate complex and brittle regex based log parsing
- Consolidate output processing between harnesses
Approach:
- Establish a common data format for test results
- Populate data format in-harness with a standardized logging API
- Log data from test harnesses as data structures rather than formatting them into strings
Implementation
Participant Systems
- System under test (Javascript, Java, C++)
- Python test harness
- Mozharness/Buildbot
- Tbpl/Treeherder
- Blobber
Logging APIs
mozlog.structured readthedocs
StructuredLog.jsm
StructuredLogger.java