Is the level of logs adapted to the environment ?
Are trace and debug log levels disabled in production?
The deployment of services is linked to the collection of information that allows its control, such as anomaly events and debugging execution traces. These automatically generated logs are useful if they are actually used to make the service more reliable, but are a waste of resources when they are collected and ignored.
Rule for assessing the level of compliance of the criterion
0 / 0
16 other criteria related to the recommendation: Use the technical components that improve the sustainable IT aspects, security and performance
Is the documentation of the functionality available to enable its reuse ?
Is the web server used asynchronous and multi-threaded ?
Has the dependency tree of the integrated components been evaluated ?
Can dependencies be reduced by using an alternative component ?
Is the user informed of a processing in progress in the background ?
Has the integration of asynchronous processing been evaluated ?
Are unused resources freed up as quickly as possible ?
Is a VM necessary as opposed to a container solution ?
Does service availability require redundancy ?
Do interactions between components benefit from caching mechanisms ?
Are the browser caches not being blocked by the framework or technology used ?
Is there a lighter framework / library that meets the functional need ?
Is an Open Source solution available for the functional need ?
Are the versions of the components used tracked and deployed ?
Is the security implemented justified with regard to the operations carried out ?
Are temporary files included in the "logrotate" ?