Generally the logging is at INFO level for auditing, unless there is an entry in the policy to raise it to a higher level.
And when so then there is no entry written for the "Message Processed Successful".
It's possible you have for the "Catch All /* service an entry raising the audit status.
General recommendation is to add specific service for the F5 URL, so you can set the audit settings for that one separately to your "Catch all" default policy.
The customer did not want to adopt this approach.
The error messages are written by the "MessageProcessor" class.
We found we can set the log level for the MessageProcessor to a level above INFO then it will not print the "URL not resolved" log message.
Here is how I did it :
The class in MessageProcessor, and can be set in global cluster property log.levels :
If we set the log level to SEVERE ie above INFO messages are not displayed.
Then here in the ssg_0_0.log you can see after the cluster wide property setting we no longer get the "URL not resolved" message:
In that class rhere are only two "info" level messages:
"Request URL not resolved"
"Tracing enabled on service but no trace policy configured"
So those are the two messages that you will not see anymore after setting that log level .