May 8-11, 2017

Event Details

Please note: All times listed below are in Central Time Zone

Enhancing Log Message Headers for RT Debug and Traceability

This session will present two specifications for adding debug and traceability to log messages.

The Operators have continuously requested both of these and have made their voices heard in the meetups about this.  The following specs will be presented for discusion and improvement:

Error codes in Log Message Headers: Unique error codes provide both memorable mnemonics for operators and exact location in the code base where the message was generated.  This enhances real time debuggability during ongoing operations.  Syslog standards have a usable field for this and will register as a dash (-) if no value is present, allowing "while you're in there" improvements.

RequestID partial history in Log Message Headers: Request IDs are now part of many of the log message contents.  Operators have stated they would also like them in headres along with a way to trace back through the request to originating requests and/or folks.  The Specification will provide a method to do this through the key/value pairs field of the Syslog style error messages, utilizing three key/value pairs.

specsare forthcoming but will be available before the summit for comments and changes.  The forum should provide through discussion and real time modifications, the path to the final specs and for blueprints.

Tuesday, May 9, 12:05pm-12:45pm (4:05pm - 4:45pm UTC)
Difficulty Level: N/A
I am an industry veteran, with experience spanning computer bring up to AI, networks, mobile compute, and embedded systems. But my attention always seems to return to close to the metal, large infrastructure. Starting out in EE as a systems engineer, I migrated to SW development then on to QA and SW Process. During the journey, I have analysed Space Shuttle launch communications, modelled... FULL PROFILE