Add Winston log rotation to prevent unbounded log file growth in production

[Calebux]

Description

The Winston logger in /backend/src/services/logger.ts (or wherever it is configured) does not have log rotation configured. In production, log files will grow indefinitely until the disk fills up and the server crashes.

Current State

Winston is configured with file transports but no rotation:

new winston.transports.File({ filename: 'error.log', level: 'error' }),
new winston.transports.File({ filename: 'combined.log' }),

A busy production server logging every request and blockchain event will generate hundreds of MB per day.

Fix

Use winston-daily-rotate-file:

npm install winston-daily-rotate-file

import DailyRotateFile from 'winston-daily-rotate-file';

const transport = new DailyRotateFile({
  filename: 'logs/application-%DATE%.log',
  datePattern: 'YYYY-MM-DD',
  zippedArchive: true,
  maxSize: '20m',      // rotate when file reaches 20MB
  maxFiles: '14d',     // keep 14 days of logs
  level: 'info',
});

const errorTransport = new DailyRotateFile({
  filename: 'logs/error-%DATE%.log',
  datePattern: 'YYYY-MM-DD',
  zippedArchive: true,
  maxSize: '10m',
  maxFiles: '30d',
  level: 'error',
});

const logger = winston.createLogger({
  transports: [transport, errorTransport],
});

Additional Steps

• Add logs/ directory to .gitignore
• Configure log level via LOG_LEVEL environment variable
• Add structured logging fields: requestId, userId, duration on every request
• Consider shipping logs to a service (Datadog, Papertrail, Axiom) for production

Acceptance Criteria

• winston-daily-rotate-file installed and configured
• Logs rotate daily with 14-day retention
• Old logs are gzip-compressed
• logs/ directory in .gitignore
• LOG_LEVEL environment variable respected

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[jerrygeorge360]

@jerrygeorge360 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

hello. I will like to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jerrygeorge360 to this issue.

[drips-wave]

Congratulations, @jerrygeorge360! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @jerrygeorge360: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊