# Charity Majors

> ~1978– · Engineer, Co-founder of Honeycomb
>
> **Recorded contribution:** Honeycomb; observability movement; operations engineering

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Charity Majors worked on large operational systems including Parse before co-founding Honeycomb with Christine Yen in 2016. She became a prominent advocate for observability: the ability to ask novel questions of a production system from richly structured events, rather than predeclaring every metric and dashboard. Her contribution joins product design, operational practice, and forceful public pedagogy.

## 2. The problem inherited

Distributed services failed through high-cardinality, request-specific interactions that fixed dashboards and unstructured logs could not efficiently isolate.

## 3. The central contribution

Majors co-founded Honeycomb and helped define modern observability practice around high-cardinality structured events, exploratory queries, and production ownership by software teams.

## 4. Reconstruct the mechanism

1. Emit one richly structured event for each meaningful unit of work, often a request.
2. Preserve identifiers and dimensions that distinguish users, builds, endpoints, and dependencies.
3. Aggregate and slice events interactively to find the earliest divergent population.
4. Turn the discovered mechanism into tests, alerts, and a bounded operational intervention.

## 5. What changed downstream

- The observability movement shifted attention from predetermined monitoring toward exploratory debugging of unknown failures.
- It helped connect software delivery, ownership, and production feedback instead of treating operations as a separate downstream team.

## 6. Attribution, limits, and uncertainty

- Observability ideas have many predecessors in tracing, event logging, statistics, and site reliability; Honeycomb is a team and company achievement.
- High-cardinality telemetry can be expensive and privacy-sensitive, and exploratory tooling cannot repair poor hypotheses, missing events, or unsafe data collection.

## 7. Reconstruction lab

Instrument a toy service with one event per request and five dimensions. Create a failure affecting one rare subgroup and find it without adding a new log statement after the incident begins. Compare the event model with a handful of pre-aggregated metrics: identify which diagnostic question can be asked only after the failure occurs. Add user identifiers and secrets, then design field-level controls, retention, and sampling before sending data. Calculate the cost of retaining every high-cardinality dimension. The result should preserve the insight behind observability while exposing its boundary: flexible evidence improves debugging only when instrumentation semantics, privacy, and storage economics are deliberately governed. Test whether two engineers can derive the same meaning from an event field, since cardinality without stable semantics produces flexible but unreliable queries.

## 8. Evidence trail

- [Charity Majors](https://www.honeycomb.io/author/charity) — Honeycomb
- [Observability: A 3-Year Retrospective](https://www.honeycomb.io/blog/observability-a-3-year-retrospective) — Honeycomb

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*