...
- New Work Items:
- Luke to work with doc team on high level what's new and MDC details as part of
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-107 - Check on closing sprint - michael
- version using branch on our RTD - michael
- Filebeat easier in HEAT because all work is in integration team - michael (get epic)
- Discuss how to get http request/session key:value pairs all the way down to the DAO layer - REST API should handle this - verify the code abstraction from example JAX-RS 1/2
(No manditory adoption: servlet filter - maybe no - give the projects an RI on a single project and reference this - Need to audit all the project - unavoidable to enumerate what API is used for HTTP REST access - in the terms of plugging in our requestID passing
- need to look at the code -
- Discuss how to get http request/session key:value pairs all the way down to the DAO layer - REST API should handle this - verify the code abstraction from example JAX-RS 1/2
need to review - and prioritize and merge with OOM R2 release - for resiliency (how is logging part of this)
- OOM for Production-Grade Deployments for example clustering persistence LOG M1 (Beijing) Candidates - for example how do we handle the distributed FS on a distributed ELK stack
both ELK infrastructure and a scaled SDNC cluster (a filebeat per instance and its PV)