Skip to content

[P1] Reduce per-block log volume and add --log-format=json #43

Closed

Description

@auricom

Priority: P1 (cost) · Effort: S

Problem

Each block produces at least 3 Info log lines ("processing block", "found matching commitment", "… verified on Celestia"), written through zerolog.ConsoleWriter, which is slow and not machine-parseable. At 10 blocks/s that's about 2.6M lines a day. The drift, balance and jsonrpc exporters also log at Info on every successful poll.

Proposed fix

  • Move per-block and per-poll success logs to Debug; keep Warn and Error.
  • Add a --log-format=json|console flag. Default console so existing behaviour doesn't change. Document it in the README.

Pros / Cons

  • ✅ Large reduction in log storage cost; JSON output can be ingested by Loki and ELK.
  • ⚠️ Less output by default. The self-observability metrics issue covers most of what those logs told you.

Activity

  1. auricom commented on Oct 20, 2026

    @auricom
    CollaboratorAuthor

    Note: #33 adds another Info-level log per verified header ("blob verified on Celestia" in VerifyBlobAtHeight). Include it when moving per-block logs to Debug.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions