## Progressive Summary ### Executive Summary (Layer 3) **Charity Majors (Honeycomb co-founder) argues that "observability" has been diluted from its original meaning—exploratory, open-ended investigation of systems—to a marketing buzzword. The term once stood for specific technical prerequisites (high cardinality, high dimensionality, traceability, structured events, rich context, end-to-end instrumentation, user-perspective focus) that enabled genuine system understanding.** ### Key Insight (Layer 2) > "'Observability' once meant the kind of exploratory, open ended investigation our systems increasingly demand." ### Context (Layer 1) - **Source**: Charity Majors (@mipsytipsy), Twitter/X, October 31, 2023 - **Author Background**: Co-founder of Honeycomb, former Parse/Facebook ops lead, observability pioneer - **Platform**: Twitter thread (12.5K views, 115 likes, 17 reposts) - **Date captured**: October 31, 2023 (screenshot) ### Cross-Domain Connections - **Software Engineering** - Core observability principles and their technical requirements - **[[Development Philosophy]]** - Systematic understanding vs. surface-level monitoring - **First-Principles Thinking** - Definition precision matters for effective practice ### Discoverability Score: 7/10 Relevant for software engineering philosophy, DevOps/SRE practice, and the meta-pattern of term dilution in technical fields. ### Verification Status [Verified] - Screenshot of Twitter/X post from @mipsytipsy dated 10/31/23 --- ## Original Content ![[Screenshot 2023-10-31 at 04.21.47.jpeg.png]] --- ## Key Extracted Concepts ### Observability Definition Erosion "Observability was supposed to *mean* something, and in the early days, it did." The term has been co-opted by vendors selling traditional monitoring tools, diluting its original technical meaning. ### True Observability Prerequisites According to Majors, observability originally required: - **High cardinality** - ability to distinguish individual entities (user IDs, request IDs, etc.) - **High dimensionality** - many attributes per event - **Traceability** - following requests through distributed systems - **Structured log events** - machine-parseable, queryable data - **Rich context** - comprehensive metadata about each event - **End-to-end instrumentation** - visibility across entire request path - **User perspective focus** - "from the user's perspective -- each user's" ### Old Tools vs. New Requirements "You can't get it using old fashioned tools" - traditional monitoring (metrics, dashboards, alerting) doesn't provide the exploratory capability that modern distributed systems require. The prerequisites above are what differentiate observability from monitoring. ### Industry Pattern: Definition Capture Technical terms get captured by marketing, losing precision that made them useful. This pattern repeats across tech: "agile," "DevOps," "microservices," and now "observability." --- ## Synthesis Notes **Relationship to Existing Topics**: 1. **Software Engineering** - Observability is a core capability for modern systems. Majors' definition connects to [[SRE Evolution Framework]]'s "outside-in" user experience optimization principle. 2. **Development Philosophy** - The emphasis on exploratory investigation over dashboards aligns with systematic understanding approaches. "Open-ended investigation" is first-principles debugging. 3. **Strategic Communication** - Term dilution is a strategic risk. When important concepts lose precision, practitioners lose the ability to communicate requirements clearly. **Atomic Concept Extracted**: - [[True Observability Prerequisites]] - Extracted to Software Engineering *Source: [External Link](https://charity.wtf/2020/03/03/observability-is-a-system-property-monitoring-is-for-actions/)*