redpanda-data / redpanda-data/redpanda

Logging of admin and other critical operations should be at WARN level not at TRACE level

Open
#3,741 4 comments 0 reactions 1 assignee View on GitHub

@esteban is already working on this.

Since Feb 5, 2022.

area/redpanda kind/enhance supportability
Dominant language
C++
Stars
12.6k
Forks
792
PR merge metrics
No merged PRs in 30d

Description

Version & Environment

Redpanda version: v21.11.3

Altering configurations, ACLs or any other property that is critical to Redpanda should be logged at WARN level and not TRACE level.

What went wrong?

When altering a critical property such as retention.ms in a topic, our default INFO level logging will no leave trace of that request making hard to identify changes made by users even if they have been authorized.

JIRA Link: CORE-838

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.