effect-v4-observability

Instrument Effect v4 public boundaries with named spans and structured logging.

2|Updated Jul 2, 2026

Search Tags:#logging #metrics #observability #tracing #opentelemetry #effect

Ready to run

npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-observability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: effect-v4-observability
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-v4-observability
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of implementing consistent observability in Effect v4 applications by enforcing a strict separation between domain logic and infrastructure-level telemetry.

Core Features & Use Cases

Boundary Instrumentation: Provides patterns for using Effect.fn to instrument public fallible boundaries with named spans.
Telemetry Agnosticism: Guides developers on keeping pure-tier libraries free of OTel dependencies while ensuring apps can compose telemetry at the edge.
Metric & Log Management: Offers best practices for structured logging and metric tracking using the updated Effect v4 Metric surface.

Quick Start

Apply the effect-v4-observability guidelines to instrument your public service boundaries with named spans and structured logging.

Frequently Asked Questions about effect-v4-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement observability in Effect v4 without coupling domain logic to OpenTelemetry?▼

To implement observability without coupling domain logic, keep pure-tier libraries free of OTel dependencies and compose telemetry at the application edge using Effect.fn to instrument public fallible boundaries.

What is the best way to standardize structured logging and metrics in Effect v4?▼

Standardize structured logging and metrics in Effect v4 by applying consistent span naming, fiber-aware logging, and the updated Effect v4 Metric surface to track domain-agnostic library operations.

How do I instrument public fallible boundaries with named spans in Effect?▼

Instrument public fallible boundaries in Effect by using Effect.fn to wrap operations with named spans, ensuring consistent telemetry composition at the infrastructure level without modifying pure domain logic.

Does this observability approach require adding OpenTelemetry dependencies to my domain-agnostic libraries?▼

No, this observability approach enforces a strict separation by keeping domain-agnostic libraries free of OTel dependencies, allowing apps to integrate OpenTelemetry at the application edge instead.

Why should I use fiber-aware logging for Effect v4 applications?▼

Fiber-aware logging is required for consistent observability in Effect v4 to accurately trace concurrent operations, ensuring structured logs maintain proper context across asynchronous fibers.

When should I apply telemetry composition at the application edge in Effect?▼

Apply telemetry composition at the application edge when instrumenting public service boundaries, ensuring domain logic remains pure while the app handles span naming, logging, and OpenTelemetry integration.