Severity Evaluation 

Use

The message logging depends largely on its severity level, compared with the severity threshold assigned to the source object. In some cases, it is not advisable to call the output API (logT, fatalT, errorT, and so on), due to potential performance issues. For example, resolving the parameter list of the call.

An additional severity check before making the output calls is required. There are APIs that enable you to do this, and you can find them in the LogController class:

beLogged(Severity level) beFatal(), beError(), beWarning(), beInfo(), bePath(), beDebug()

 

This returns a Boolean trueif the message passes the respective severity level check. Otherwise it returns false.