Architecture #7533
closedUnits of measurement cleanup in logs (millisec --> ms)
Description
Hi,
since I just had this scrolling by:
This output uses the following units:
- ms
- milliseconds
- millisec
- missing (13737)
[2015-12-02 12:55:15] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Inventory 'xxxxxxx-2015-10-28-15-37-04.ocs' parsed in 420 milliseconds, sending to save engine.
[2015-12-02 12:55:20] INFO com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report file processed in 5 seconds and 293 milliseconds
^[[B[2015-12-02 13:02:36] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - All relevant information fetched in 1304194ms, start names historization.
[2015-12-02 13:02:40] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Historization of names done in 4212ms, start to build rule values.
[2015-12-02 13:02:40] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals built in 34ms, start to expand their values.
[2015-12-02 13:02:40] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Global system variables built in 13ms, start to build new node configurations.
[2015-12-02 13:02:54] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node's target configuration built in 13737, start to update rule values.
[2015-12-02 13:02:58] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals updated in 4479 millisec, start to detect changes in node configuration.
makes your life harder than it needs be.