This repository was archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Further reduce INFO logging #8021
Copy link
Copy link
Open
Labels
A-LoggingSynapse's logs (structured or otherwise). Not metrics.Synapse's logs (structured or otherwise). Not metrics.O-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceAffects or can be seen by most users regularly or impacts most users' first experienceS-TolerableMinor significance, cosmetic issues, low or no impact to users.Minor significance, cosmetic issues, low or no impact to users.T-EnhancementNew features, changes in functionality, improvements in performance, or user-facing enhancements.New features, changes in functionality, improvements in performance, or user-facing enhancements.T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Description
Some candidates that could be removed from default logging:
OPTIONS
request processing (~7% of log lines on jki.re)/sync
request processing (~7% of log lines on jki.re, ignoring INFO)Sending request
(~12% of log lines on jki.re)Received txn from
(~11% of log lines on jki.re), though we probably(?) want to somehow log how many PDUs the transaction contained in the processing request log line (or maybe have a generic "how many new events were persitsed" like we do fordbevts
)
ptman
Metadata
Metadata
Assignees
Labels
A-LoggingSynapse's logs (structured or otherwise). Not metrics.Synapse's logs (structured or otherwise). Not metrics.O-FrequentAffects or can be seen by most users regularly or impacts most users' first experienceAffects or can be seen by most users regularly or impacts most users' first experienceS-TolerableMinor significance, cosmetic issues, low or no impact to users.Minor significance, cosmetic issues, low or no impact to users.T-EnhancementNew features, changes in functionality, improvements in performance, or user-facing enhancements.New features, changes in functionality, improvements in performance, or user-facing enhancements.T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.