Add logging to backend/services/FileStorageService.ts

[Nathydre]

• Files to modify : backend/services/FileStorageService.ts
• Acceptance Criteria :
  • Log all file operations (upload, download, delete)
  • Include relevant metadata (file name, user ID, timestamp)
  • Use structured logging format

[samad13]

I’d like to apply to work on the issue regarding logging file operations in backend/services/FileStorageService.ts. I have experience implementing structured logging in Node.js/TypeScript projects using libraries such as Winston and Pino, and I understand the importance of traceability and observability in backend services. I am confident I can deliver a clean, maintainable solution that enhances transparency and debugging capabilities in the system.

[Ebenezer199914]

can i work on this issue

[Tobi-8]

please can i be assigned?

Hey maintainer, i have looked through your description, and i have had experience in this type of issue.
kindly assign

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[diegomancera71-art]

The problem genuinely excites me — observability in a Stellar-powered payments platform is exactly where good engineering decisions have real consequences.
I'll wrap upload, download, and delete with a try/finally timing block that fires a structured JSON event on every outcome and re-throws errors unchanged. Logger injected via constructor (no new deps, swappable for pino). Schema covers fileName, userId, timestamp plus durationMs and errorCode for NEPA's analytics and cross-service tracing.
2 files, 0 new dependencies, 0 breaking changes. PR open today. Point me to any existing logger in the codebase and I'll align.