Skip to content

Backend structured logging conventions #565

Closed

Description

@codebestia

Write apps/backend/docs/concepts-logging.md for lib/logger.ts: the structured logger, log levels, the standard fields, and — most importantly — the rule that message content, ciphertext and key material never appear in a log line.

Acceptance criteria:

  • Documents the logger configuration, levels, and how level is set per environment
  • States the no-content rule explicitly and gives the safe way to log about a message (ids and counts, never bodies)
  • Documents the standard correlation fields available for tracing a request or socket event
  • Notes the places still using bare console.* and that new code should not add more

Activity

  1. chiomailekuba commented on Aug 27, 2026

    @chiomailekuba

    @chiomailekuba has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    GM

    i'm a blockchain developer

    please can i work on this issue

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

  2. Dannyorji commented on Aug 30, 2026

    @Dannyorji
    Contributor

    @Dannyorji has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi Maintainer
    Can i be assigned this?

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

  3. drips-wave commented on Aug 31, 2026

    @drips-wave

    Congratulations, @Dannyorji! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @Dannyorji: 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 🌊

  4. github-actions commented on Aug 31, 2026

    @github-actions

    Closed by #598, merged into dev.

  5. drips-wave commented on Aug 31, 2026

    @drips-wave

    This issue has been completed by @Dannyorji as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @Dannyorji: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions