Issue 174 - Logging

[nigelgbanks]

For Issue-174 this removes the use of symlinks and instead appropriately configures the logging for each service using the recommend methods according to their documentation.

There is one notable exception handle still uses symlinks to get the services to write to stdout/stderr as there is no other method possible in its cases as the logging is hard coded in the application to write to specific files at specific path.

[nigelgbanks]

Lost some time debugging failing tests on my M1 Macbook, need to upgrade Gradle when the next release is minted to get
gradle/gradle@9059e16 currently we cannot perform tests on M1.

[nigelgbanks]

The failing test is caused by an odd karaf behaviour in that when it first starts up it writes to karaf.log before the loggers are configured so the first few lines of output go there. The tests is looking for these lines and timing out.

[nigelgbanks]

God that was hard to debug for 88f7aa6 at least now I know how to use jdb.

This is now ready for review.

[rosiel]

From tech call: is it possible to get some testing instructions?

[nigelgbanks]

Broadly speaking to test, is that it works and logs are generated to standard out.

[g7morris]

Hi @rosiel

Great question, apologies for the late reply.

Hopefully my response below could be copied to isle-dc documentation or to a different location that works for folks in addition to this location? If not, no worries we'll at least have this process captured in this repo.

I've made a new PR for this process if you have time to review #212

Happy to help as needed here.

@nigelgbanks Feel free to add anything I may have missed.

[Edit] I originally posted everything here as a response and realized it should just be a draft doc to work on instead. Sorry for the dump folks.

Thanks,
Gavin

[g7morris]

Tested and this passes as noted here #174

@nigelgbanks Ship it.