Log cleanup, phase 2
Current situation
Java logs have been simplified, which is great. But they are still confusing and overly verbose.
Here are some examples:
[ ] [job 290b2978-a7d5-4d91-b200-e138f3b96fb0] [DEBUG] Received execution command cae3a639-86a2-4a1d-8a48-972af3e78d4d for job 290b2978-a7d5-4d91-b200-e138f3b96fb0
[ ] [job 290b2978-a7d5-4d91-b200-e138f3b96fb0] [DEBUG] Received execution result cae3a639-86a2-4a1d-8a48-972af3e78d4d for job 290b2978-a7d5-4d91-b200-e138f3b96fb0
[ ] [job 290b2978-a7d5-4d91-b200-e138f3b96fb0] [DEBUG] Converted message : org.opentestfactory.plugins.result.aggregator.domain.NonHandledMessage@1e4e2889
[ ] [job 290b2978-a7d5-4d91-b200-e138f3b96fb0] [DEBUG] Converted message : org.opentestfactory.plugins.result.aggregator.domain.NonHandledMessage@4e152284
[ ] [job da826754-9cee-4c68-a107-26ecc639836d] [DEBUG] Received unexpected suite definition receipt for suite 8aaa853285a2aa730185a5288de80000, ignoring.
[ ] [job 290b2978-a7d5-4d91-b200-e138f3b96fb0] [DEBUG] Received execution result cae3a639-86a2-4a1d-8a48-972af3e78d4d:null for job 290b2978-a7d5-4d91-b200-e138f3b96fb0
Some ideas of improvements:
- job IDs should not be present in the notification text
- the 'converted messages' notifications are useless
- what does the ':null' means in the last debug notification?
Those should be traces, not debug notifications:
[ ] [DEBUG] Checking if attachment /tmp/290b2978-a7d5-4d91-b200-e138f3b96fb0_31_output.xml matches the POSTMAN technology
[ ] [DEBUG] Checking if attachment /tmp/290b2978-a7d5-4d91-b200-e138f3b96fb0_31_output.xml matches the KATALON technology
[ ] [DEBUG] Checking if attachment /tmp/290b2978-a7d5-4d91-b200-e138f3b96fb0_31_output.xml matches the UFT technology
[ ] [DEBUG] Checking if attachment /tmp/290b2978-a7d5-4d91-b200-e138f3b96fb0_31_output.xml matches the RANOREX technology
A more complete example is in the comments of: tools!79 (merged)