Skip to content

[Observability] Redact secrets and personally sensitive fields from structured logsΒ #926

Description

@ayomideadeniran

πŸš€ Feature Overview

Create one reusable redaction policy for tokens, passwords, authorization headers, private keys, and high-risk identifiers.

πŸ› οΈ Implementation Requirements

  • Keep the work scoped to the named service boundary.
  • Use explicit types, validation, safe failure behavior, and structured operational signals.
  • Preserve backwards compatibility or document a migration plan.
  • Add focused unit and integration tests for normal and failure paths.

πŸ”§ Technical Specifications

Node.js, TypeScript, Express, Prisma, Redis, queues, and Stellar services as applicable.

βœ… Acceptance Criteria

  • Redaction applies before log output; nested values are handled; original error context remains useful; tests prove secrets never appear.
  • No sensitive data is exposed through responses or logs.
  • Relevant CI checks pass.

πŸŽ“ Difficulty Level

Intermediate to Advanced.

⏱️ Timeline

ETA: 2 days

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions