I don't really agree. The more similar your test environment is to your production environment, the fewer problems you will miss before deploying. So I think your development logging levels should be the same as your production logging levels, except when you are actively debugging something. Which should not be a frequent occurrence.
Joined: Jan 06, 2003
We have a "production-like" environment too. In any case, I would like to know how this configuration change across the landscape maintained.
If you want something to be different in two deployments of an application, and you don't want to make last-minute edits before deploying to achieve that, then it follows that the difference must be configured outside the application. How you achieve that depends on where you are deploying your application.
(I suppose I don't have much sympathy for your logging example because we use logging as part of our business rules. For example we might write an entry to the log file when we got the orders from customer ABCD. Then when we have a hypothetical dispute with customer ABCD, we can see when the orders came in and whether they were consistently late, or something like that. We rarely use logging as a debugging or development tool. But that doesn't do anything to answer your question.)