Hello,
when the Log-prefix is too long, the prefix-string in the LOG will be shorten.
Maybe this limit can be extended - or better, the user should be able to decide the maximum length of the entry which will be shown in LOG.
On the attached picture you see that the prefix was cut (instead of “…chain_443” only “…chain_44” will be shown)
Moreover, it would be a nice feature when in the LOG list the number of the rule will be shown which occurs the log entry. 
If I counted your screen capture right, that allowed 31 characters (can’t say that I had ever counted that before). It’s supposed to be the log PREFIX - not the entire log entry. 31 characters seems overly generous in my humble opinion.
Some comments are longer than 31 characters.
It would be no problem if there will be an user-defined length be implemented.
Moreover, the ID of the rule in the beginning of each line on LOG which occurs an log entry would be helpful (F13 for filter rule #13, N14 for NAT rule #14 for example).