Hi Francesco, > Gesendet: Dienstag, 10. September 2013 um 15:18 Uhr > Von: "Francesco Chicchiriccò" <ilgro...@apache.org> > An: dev@syncope.apache.org > Betreff: Re: EntityValidationInterceptor / log level of bean validation errors > On 10/09/2013 13:27, Guido Wimmel wrote: > > currently, EntityValidationInterceptor logs bean validation errors with log > > level ERROR. > > > > I think bean validation errors can be part of normal system behaviour (e.g. > > a user registers > > itself or is registered by an admin and accidentally or unknowingly enters > > invalid data and > > then gets an error message on the UI). > > > > We configured our system to send notifications to the operations team on > > ERROR log events and > > would have to filter this one out. > > > > I'd suggest turning the log level to WARN or maybe even INFO, but it can > > also be that I have overlooked > > some use cases where ERROR would indeed be appropriate. > > Hum, not sure I agree: are you suggesting that a bean validation error > is not an actual operational error, hence it shouldn't be logged as > ERROR? I can hardly figure them out as WARN...
I wouldn't consider it an operational error when a user enters invalid data into a form (e.g. the self registration form) and on a save attempt gets a response back that the data must be corrected. IMO this is part of regular operation where I wouldn't expect any ERROR log events. But maybe there are other cases of bean validation errors that indeed justify ERROR, or the concept of the ERROR log level is a different one here than I have in mind. Cheers, Guido
