It wasn't putting the IP in the log but in the database and along the username and session data, there is an open ticket about that behavior too. Since I'm in Europe/Germany, this kind of data storage would have been a no-go even before the GDPR.
It sounds like you had to remove the Trackable module from Devise - which would indeed be one line of code to change in a Rails app, but quite hard to figure out if you didn't know. However, Devise is a third party gem which is often used with Rails but isn't actually a part of Rails, so can you really blame Rails for this? (And, unless it's for a very specific string, is grepping a codebase that you have no understanding of ever really a successful strategy?)
I blame the coding practises of the rails devs, not the gem itself.
Grepping can be a successful strategy, esp. when you know what you are looking for and you can search the database column in the code
I can't in all honesty understand why you wouldn't just Google "rails login current_sign_in_ip", the top three hits for which would probably all put you on the right track. I would say grepping through the code of third-party libraries would be something I'd do only in desperation when working in an unfamiliar codebase. But hey, each to their own!
Usually you'd just create a custom logger[0] and tell Rails to use it[1]
[0] https://ruby-doc.org/stdlib-2.5.0/libdoc/logger/rdoc/Logger....
[1] https://guides.rubyonrails.org/configuring.html#rails-genera...