Meteor needs a standard instrumentation seam — the design is done and de-risked (read-only lifecycle events for methods, publications & DDP)

Meteor has no standard way to observe its own lifecycle. To add structured logging, an APM (Datadog/Honeycomb), OpenTelemetry, Sentry, or even a small dev/debug panel, you have to monkey-patch Meteor.methods , publications, and DDP — privately, fragilely, redundantly, and it breaks across versions. I’ve taken this past the idea stage : a full design, the technical risk validated with a runtime spike , and the one prerequisite fix already up as a PR . It’s a small, stable, read-only lifecycle instrumentation seam — and the punchline is that it can be built quickly and without risk , because the