Design and Develop a Logging Service and Test Client

THE TASK Design and develop a logging service and a test client that could be used for various future assignments and projects. REQUIREMENTS It is up to you to determine the information that you will log and the format you intend to use. You must meet the following requirements: • The service will be network based. It will listen for logging messages on either TCP or UDP (your choice). • The service may be developed in any language you wish – suggestions include Java, Python, or Go (other languages may be acceptable – you must ask before using them though.) • The service will store logging information in text files. • The service does not need a UI (command line is OK) • You must use a config file or command line arguments – no-hard coded paths or addresses. • You will have to research what features a good logging service should support. • You will create a client tool to test your service. o This must be developed in a language different than the logging service or a penalty will apply. o This tool should allow for manual testing of your service. o This tool should be able to run a thorough set of automated tests on your logging service. • You will lose ALL marks for SET standards if you don’t use good naming in your code • Demonstration is REQUIRED or you will not receive a grade Please note that it is up to you to develop a GOOD logging solution – appropriate service information and configurability. You must do some additional research to do so. WHAT TO SUBMIT Please submit a single cleaned zip archive containing both parts of your solution. RESOURCES Linux and Unix have a logging service called syslog. You are not duplicating syslog, but you can definitely learn a lot from it. https://stackify.com/syslog-101/ Tips on logging microservices: https://logz.io/blog/logging-microservices/ PENALTIES / CAPS The following penalties / caps will apply: • Test client written in same language as service – 20% deduction • Test client must run on same machine as logging service – 40% deduction • Not possible to run multiple logging clients simultaneously – 20% deduction NOTES Logging service tips: • Your logs must be stored in a single, plain text file. • Your log message format should be configurable. • Your logging service must be designed in a way that multiple simultaneous clients can be used and identified. • The content of your stored logs is up to you; you must do some research to determine what should be there. • Reading, filtering, or displaying your logs is completely out of scope. o Writing a log viewing tool is a waste of your time. o Use a tool such as lnav (http://lnav.org/) to view and filter logs. o Your log file format should support using common tools (Notepad++, Vim, lnav, etc.) • Your logging service must prevent abuse from mis-configured or overly noisy logging clients o Consider the case where a logging client may accidentally be sending debugging messages Test client tips: • Your test client must allow you to send manually configured log messages of any type that your service supports • You should be able to run two instances of your test client to generate logs • Your test client must include the ability to test and demonstrate your service abuse prevention • Your test client must include the ability to automatically test all log formats and message types that your service supports • Your test client is not an interface for your logging service, only a test client. Your logging service operates independent of your test client.