← Graph

Instrumentation as events, independent of output

question 3 connections

Audience member observes that payloads still carry an interpolated content string and asks whether the architecture should be code instrumented with generic events that listeners later fan out to logs, traces, metrics, or analytics. Callaghan enthusiastically agrees and cites Charity Majors' 'events all the way down'. He's building toward a value-object Event, published via event.publish onto ActiveSupport::Notifications, with listeners dispatching to Datadog, Dynatrace, Segment, PostHog, etc. Only nuance: traces additionally need hierarchical context threaded through events.

answer_summary
Yes — 'events all the way down' (Charity Majors). Callaghan is building a value-object Event + event.publish on ActiveSupport::Notifications with pluggable listeners to any observability or analytics tool. Caveat: tracing needs hierarchical context on top of plain events.
question Instrumentation as events, independent of output
about
Question directly describes the events-all-the-way-down architecture.
question Instrumentation as events, independent of output
about
Callaghan cites Charity Majors in his answer.
question Instrumentation as events, independent of output
asked_at
Final Q&A question framing instrumentation as events with pluggable sinks.

Provenance