Jonathan Ellis created CASSANDRA-18517: ------------------------------------------
Summary: Make Cassandra more user-friendly (admin-friendly) by cleaning up logging Key: CASSANDRA-18517 URL: https://issues.apache.org/jira/browse/CASSANDRA-18517 Project: Cassandra Issue Type: Bug Components: Observability/Logging Reporter: Jonathan Ellis Assignee: Jonathan Ellis At a very high level we see two types of users: 1. Early adopters generally want to understand Cassandra's design, how the pieces fit together, and why 2. Mainstream users just want it to work, preferably with as little attention from them as possible Group 1 loves verbose logs because it helps them figure out what's going on under the hood. Group 2 sees verbose logs as intimidating ("this is going to be hard") if not scary ("this isn't debugged enough yet"). Early on, group 1 users predominate. But there's way more group 2 users out there now and as Cassandra sees more adoption it will primarily come from them. It's time to start optimizing for group 2. Group 1 is, after all, completely capable of adjusting the log levels themselves when necessary. A good rule of thumb is, "is this necessary information for my day-to-day operation of the system." If not, it should be at debug (or sometimes trace). Compare [our startup logging|https://gist.githubusercontent.com/jbellis/a1f324c145c4d46c3409969393b24077/raw/a767e4b92c29a51130940326de619a3c418096b7/gistfile1.txt] with [postgresql's.|https://gist.githubusercontent.com/jbellis/a9585d3f04f49c7e3685c9122975d51b/raw/beea37fd0834d1c8f38e5c1667623aa37598d3dd/gistfile1.txt] -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org