OneRM Backend

Problem¶

The fetchers println entire response bodies:

• IikoOlapV2RequestsFetchingService.fetchOlapData:55 — println(responseBody), the whole OLAP report
• IikoServerEmployeesFetchingService.fetchEmployees — println(responseBody), the whole employee XML
• IikoAuthTokensFetchingService.fetchToken — prints the token itself (a credential in the log)
• IikoOlapV2RequestsFetchingService.fetchOlapData:37 — prints the url, which carries ?key=<token>
• IikoStatsGatheringService.getMetricValuesFromIikoDateDesc — several printlns per day iteration (lines 123, 130, 179)

The daemon runs these under nohup, so every byte is a synchronous write to nohup.out, and the loop truncates that file between steps (echo "" > nohup.out). At hundreds of thousands of requests per round this is a meaningful share of wall clock, and it leaks the IIKO session token into a file on disk.

Proposed change¶

• Replace payload printlns with SLF4J logger calls at DEBUG.
• Never log the token or a url containing key= — redact.
• Keep a small amount of INFO-level progress output (per company / per metric), not per day and not per payload.

Acceptance¶

• A normal run produces bounded, human-readable progress output.
• No token or key=-bearing url appears in the log at any level.