Page Comparison

TODOAttendance: Amdocs and AT&T. 

Minutes:

1. Introductions
2. Walkthrough of proposal.
3. Line format, separators, and the need to align provider with Elastic Stack shipping and indexing configuration.
4. Escaping, and the problem of legacy Log4j 1.X providers in controllers. (No escaping support).
5. Files, providers, minimizing classpath changes, and the implications for streams and other transports.
6. No volunteers to update logging guidelines so far. (No mandate yet anyway).
7. Transaction IDs and tracing.
8. Elastic Stack pipeline, status, deployment.
9. Lee will speak with EELK developers about default provider configuration. Main issues are:
   1. Escaping
   2. Line format
   3. MDC name-value pairs.
10. Options for getting a mandate for making changes:
    1. Logging guidelines (soft mandate)
    2. TSC (hard mandate)
    3. Mailing lists

Next time:

1. Line format revisited:
   1. Escaping and separators. 
   2. Constraints: classpath, etc.
2. Logging guidelines revisited.
   1. Line format: IMPORTANT. 
   2. Destination: IMPORTANT. 
   3. Tracing: IMPORTANT.
   4. Everything else: LESS IMPORTANT. 
3. Markers:
   1. Use in analytics
   2. EELF support
4. Transaction IDs and tracing:
   1. Headers and MDCs:
      1. Existing. 
      2. New.
   2. Zipkin (raised by Roger Maitland).
5. Michael O'Brian's work on artifacts, deployment, transactions, collaboration, demos.