@domusjs/observability — Introduction
The Observability Module in DomusJS provides a robust, plug-and-play integration with OpenTelemetry to enable:
✅ Distributed tracing
✅ Application-level metrics
✅ Centralized, traceable logging
It’s designed to give you deep visibility into your system’s behavior across commands, queries, events, jobs, and HTTP requests.
Why Use the Observability Module?
Section titled “Why Use the Observability Module?”Modern applications are often distributed and complex. To debug, optimize, and monitor effectively, you need observability — the ability to answer questions about internal states based on external outputs.
The Observability Module gives you:
| Feature | Benefit |
|---|---|
| Distributed Tracing | Track requests across services and layers |
| Metrics Integration | Collect performance and usage metrics |
| Traceable Logging | Link logs directly to traces and spans |
| Pluggable Exporters | Send data to SigNoz, Datadog, Jaeger, etc. |
✅ You can start simple (console export) and expand to full-fledged monitoring systems as you scale.
When Should You Add Observability?
Section titled “When Should You Add Observability?”- When you need to trace slow requests or jobs across systems.
- When you want to analyze performance bottlenecks.
- When you’re moving to microservices or asynchronous architectures.
- When you want to standardize tracing and metrics collection.
In the next section, you’ll learn how to configure, instrument, and extend the observability capabilities in your DomusJS project 🚀