Skip to content

TASK: Define structured logging and redaction contract #92

Closed

Description

@ramioooz

Parent: STORY: Implement centralized logging with OpenSearch

Define the portable structured-log contract and the boundary between application logging, collection, storage, and audit records.

Acceptance criteria:

  • Required fields include timestamp, level, service, environment, correlation ID, trace ID, logger, and message.
  • Spring Boot services emit one structured JSON event per line to stdout or stderr.
  • Service-side responsibilities are separated from Fluent Bit and OpenSearch responsibilities.
  • Multiline exceptions have an explicit ingestion strategy.
  • Authentication credentials, tokens, OTP values, account data, and customer PII are prohibited or redacted.
  • Operational logs are explicitly distinguished from immutable business and security audit records.
  • The relationship to distributed tracing is documented.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions