...
Michael away for a customer demo trip
must do
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
From Luke (moved from 2018-04-06 page
Notes:
- Quick meeting in Michael's absence.
- Stepped through the canonicalized multi-appender logback config:
- Appenders for Beats, EELF, and (human-readable) console.
- Parameters extracted to the top: rollover, component/subcomponent names, paths, etc.
- Parameters are the candidates for Helm templating:
- So they'd come from values.yaml.
- And the rest of the doc would be boilerplate in many cases.
- 220+ lines. So it's far from small, even at its most minimal. (Most instances will have additional logger → level mappings).
- To forward templated config to Dave and Lee to review with EELF stakeholders.
- A session to review Beijing guidelines was requested:
- (Really sorry, but I didn't catch who asked. It was somebody with an AT&T ID as their zoom handle).
- Specifically regarding conventions.
- Semantics of tokens also mentioned, which we know still needs further clarification. .
- Non-urgent. Can schedule during our next session.