I think that this case is serious gap in Ignite maintainability 1. This is business as usual case and client application can create an incorrect API call. User error should be returned back to user via the same API 2. Exception in the Ignite log file should cause an alert for application operations. Most common case for monitoring setup is to parse log file in realtime and create an incident in case if ERROR or Exception is detected. The only way for admin is to mute the false alert, and 3. Current approach is adding a lot of noise into the application logs and significantly increasing logfile size. Taking in account log rotation as a good practice, we may have less useful information to maintain Ignite
-- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
