...
# | Issue/Decision | Notes | Decision |
---|---|---|---|
1 | Are the logging guidelines set by the Logging Enhancement Project suitable for a cloud environment? | ||
2 | Do we need a second appender for errors? | Meeting Notes 11/12/20 The logging enhancement team has proposed to split the log to multiple files:
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. | |
3 | The application should only logs to stdout and not in files? |
| Meeting Notes 11/12/20
|
4 | Is the file location ok? | ../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. | |
5 | Disk space | <property name="maxFileSize" value="20MB" /> Once the log reaches this value it is zipped. | |
6 | What kind of message should go with which level for logging? | See 'Summary of each logging level' below | |
7 | How should we format our logs? | logger.debug("No of Orders " + noOfOrder + " for client : " + client); logger.debug("No of Executions {} for clients:{}", noOfOrder , client); | |
8 | Should we use is log.isDebugEnabled()? | I think we should if the cost of performing the log is expensive - for example if we need to build a paramater in the log | |
9 | What logging framework to use? | We are currently using slf4j | |
10 | What kind of information to log? |
|
Summary of each logging level
Log Level | Importance |
---|---|
Fatal | One or more key business functionalities are not working and the whole system doesn’t fulfill the business functionalities. |
Error | One or more functionalities are not working, preventing some functionalities from working correctly. |
Warn | Unexpected behavior happened inside the application, but it is continuing its work and the key business features are operating as expected. |
Info | An event happened, the event is purely informative and can be ignored during normal operations. |
Debug | A log level used for events considered to be useful during software debugging when more granular information is needed. |
Trace | A log level describing events showing step by step execution of your code that can be ignored during the standard operation, but may be useful during extended debugging sessions. |
Appenders used by ONAP Projects
...