Nimbostratus
Really Sorry I'm no CLI expert. But Hopefully if I explain the GUI side you'll be able to convert.
So from my experiance and f5 logging and monitoring in general is a bug bear of mind which i'd love to get improved!
The Remote Logging configuation, inside the f5 litterly sends everything including debug to the syslog server from what i can tell this is a legacy thing.
But there is a newer way of doing it!
You Setup a new pool with your syslog server in it.
Then a log Destination
then a log Publisher and lastly a
Log Filter
The log filter is then the part where you should be able to put somethng in to help your use case.
I think you'll also need to create two Log Destinations, one for remote syslog and one for high speed logging so its then uses this new method. But just look out now, the message now will come out of a tmm interface not the kernal interface dependant on your routing table!
Was caught out by that the first time of getting it working!
