Event Logger Test

Goal

The goal of this test is to verify that modifications to the logging configuration file(currently logback.xml) propagate changes to the system during runtime. The following major functionality is verified by this test:

1. Logger levels can be modified during runtime
2. Logging can be turned off for specific loggers

Procedure

Acceptance Test

1. Identify which configuration file is being utilized as the default for logging.
2. Start the ODE, Kafka, and Zookeeper.
3. Attach to the ODE container through docker exec command
4. Check the contents of the Events.log file to see startup logging messages
5. Start the client application and connect it to the ODE.
6. Upload a file containing ASN.1-encoded BSM data into the web interface.
7. Check the contents of the Events.log file to see updated logging messages. (Note the time of message being delievered)
8. In a separate terminal, start jconsole
9. Connect to the ODE application via remote process
10. Modify the configuration file in the container(currently logback.xml) to turn the logging level of Events.log to "OFF"
11. Save the changes on the container
12. Using jconsole navigate to the MBeans tab at the top
13. Navigate to the operations level of ch.qos.logback folder
14. Select reloadbyfilename and input logback.xml
15. Enter the button and a dialog box saying your modification was successful should appear
16. Upload another file on the web interface noting the time the message was uploaded
17. Check the Events.log to verify no new log messages were propogated
18. Modify the configuration file in the container to turn logging level of Events.log to "INFO"
19. Save the changes on the container
20. Using jconsole navigate to the operations level of ch.qos.logback folder
21. Enter the name of the logger configuration file, logback.xml, and press reloadbyfilename button.
22. Enter the button and a dialog box saying your modification was successful should appear
23. Upload another file on the web interface noting the time the message was uploaded
24. Check the Events.log to verify new log messages were propogated