<onap-seccom@...> on behalf of "Amy Zwarico via lists.onap.org" <amy.zwarico=att.com@...>
Attached is a deck with logging requirements for the ONAP containers that we will discuss at the 20 April SECCOM meeting. These are requirements adopted from the VNF security requirements and additions from Fabian Rouzaut. There is still some work to do in combining them, so be ready for a lively logging conversation on Tuesday!
The deck only talks about security logs. Based on the logging requirements from Casablanca, applications generally deal with informational logs, error logs, audit logs and debug logs.
Where do security logs fall into that spectrum?
Kubernetes normally collects BOTH stdout AND stderr as log files. The assumption is that informational messages will be written to stdout, and error messages will be written to stderr, which is consistent with the usage of stdout and stderr for the past 50 years.
The deck continually refers only to stdout, probably because it only talks about security logs.
A LOT of the PTL discussion centered around the fact that we’re asking applications to change how they are doing logging. If we are going to ask that of applications, we need to discuss the entire spectrum of logging and not focus only on the security logs.
Hope this helps the conversation.