Dave Williamson external component using the elk stack - RequestID collision with an existing system using ONAP - what if a BSS system uses the same field
A rest call with a X-transaction-ID already provided - will process normally? but need to handle differences in how it is used - writeup
discuss impact of renaming to TransactionID -
Luke: need subcontext - for example in SO (uses requestID for DB ops)
Lee Breslau secondary: protect against malicious use of the header fields - writeup
TODO: start thinking about both of these for the security subcommittee
TODO: examples of a header with the X-transaction id and partner name for example
Finalize: # of log files (leaning on 1 log - except for debug logs causing issues) - check volumetrics (for all the logs in one stream between filebeat/logstash) - prototype this
Meeting Thu at 1130 EDT on spec review (in terms of consolidating the log files) - try to get required fields covered off in the wiki
Order: wiki
Order: MDC's output ? OPS would like an order enforced? - would need to hardcode in propertyname="pattern"
see format example sent by luke for multiple appenders