Skip to content

chore: back-port catalog debug log cleanup from enterprise#26128

Merged
hiltontj merged 3 commits intomainfrom
hiltontj/catalog-debug-cleanup
Mar 12, 2025
Merged

chore: back-port catalog debug log cleanup from enterprise#26128
hiltontj merged 3 commits intomainfrom
hiltontj/catalog-debug-cleanup

Conversation

@hiltontj
Copy link
Contributor

No issue.

There were a lot of excess DEBUG logs littered around the catalog code from the catalog refactor that were causing a lot of noise in the log output.

This reduces that noise by:

  • removing log statements that were redundant
  • simplifying what is included in log statements to make them less verbose
  • changing some DEBUG to TRACE in case that verbosity is needed in some cases
  • several >>> were removed from the beginning of DEBUG logs throughout the code

In addition, the severity of the message emitted when there are no subscribers on catalog broadcast was changed from WARN to INFO to not raise any alarms.

@hiltontj hiltontj added the v3 label Mar 12, 2025
@hiltontj hiltontj requested a review from a team March 12, 2025 15:26
@hiltontj hiltontj self-assigned this Mar 12, 2025
@hiltontj hiltontj merged commit b6cb6dd into main Mar 12, 2025
12 checks passed
@hiltontj hiltontj deleted the hiltontj/catalog-debug-cleanup branch March 12, 2025 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants