Great catch - we didn't include that rule in the demo but it's in the works. To share our thinking a little more: analysing the contents of the statement is easiest (but still quite hard) so we're nailing that down. Analysing the level requires a bit more careful understanding of what the method/code around it is attempting and where this logging statement sits (harder still). Soon we hope to nail adding statements to fresh code (where we'd have to understand where to put them, what the level should be, and then the contents).