Page Comparison

• one file only

• Later we will have a file to track who is accessing it, who is registering for the access...but we are not at that point yet

• Within the log folder we could have multiple files for:

  • debug.log
  • audit.log
  • metric.log
  • error.log

  Logs will be archived each day.

Meeting Notes 11/12/20 

https://docs.onap.org/projects/onap-logging-analytics/en/latest/Logging_Enhancements_Project/logging_enhancements_project.html#id33

The logging enhancement team has proposed to split the log to multiple files: 

• debug.log
• audit.log
• metric.log
• error.log

Toine has suggested we follow this approach but exclude error logging. 

Before making anymore decisions we will investigate this project as we have some concerns about the logging standards in the logging enhancement project.

• By doing so we can leverage Kubernetes standard logging design.

• If logging to files is provided, It would be good to also have a way to disable it to avoid file space management questions on worker nodes or pvc depending where logs files would be kept.

• For monitoring, it is more complex to operate applications that are each one using specific logs files.

• By having all applications logging to stdout, all logs can be collected in a common standard way and published and re-used anywhere that is convenient for any operations team (using filebeat or elk stack for example).

  See https://kubernetes.io/docs/concepts/cluster-administration/logging/ 

• Whether user will be using Kubernetes / Azure or single manual deployment, features capability should be the same. We should not enforce to use anything specific to achieve the same service solution.
• Many company enforce to  have those separate type of log files by security policy. Usually they store the audits logs ones.
  With log properties, you always can change the level log. And also alterate/disable the logs appenders at runtime.

Meeting Notes 11/12/20 

• Everything a containerized application writes to stdout and stderr is handled and redirected somewhere by a container engine. For example, the Docker container engine redirects those two streams to a logging driver, which is configured in Kubernetes to write to a file in json format. - use a log rotation script

• We want the logging to be easily configurable and allow for different implementations on how to collect logs. We will expose this configuration in the helm charts.  
• Our default logging will be std out as it is easily configurable. 

 ../log/${logName}.log

I think this is ok. Logs will be placed in pods once deployed. 

I think we will need to set a property in our SpringBootApplication class for the log dir.

<property name="maxFileSize" value="20MB" />

Once the log reaches this value it is zipped.

1. Never log sensitive information as plain text 

2. log all important information that is necessary to debug or troubleshoot a problem if it happens.

3. Always log decision making statements e.g. the application loads some settings from a preference file and is unable to find the file