The Effect language service should emit OpenTelemetry traces/spans for its diagnostic operations. This would enable observability into rule execution performance, helping identify slow rules and understand diagnostic latency in real-world projects.
Motivation
- Visibility into which diagnostic rules take the most time
- Ability to profile the language service under real workloads
- Foundation for performance monitoring and regression detection
Scope
- Instrument diagnostic rule execution with OTel spans
- Expose trace context so editors/tooling can collect telemetry
- Keep it opt-in so there's zero overhead when not enabled
🤖 Created by Claude on behalf of @schickling
The Effect language service should emit OpenTelemetry traces/spans for its diagnostic operations. This would enable observability into rule execution performance, helping identify slow rules and understand diagnostic latency in real-world projects.
Motivation
Scope