About Resource Monitoring

In OpenTelemetry, a resource is metadata that identifies where telemetry comes from and the system it describes. It's the key distinction separating signals you care deeply about from those you can ignore entirely.

In Dash0, everything revolves around resources because they are the core of what you care about.

Instead of focusing narrowly on individual signals like metrics, traces, or logs, Dash0 provides a resource-centric approach.

As an OpenTelemetry-native platform, Dash0 adheres to semantic conventions for defining and modeling resources, ensuring a complete picture even when data sources are fragmented.

Views

For convenient and quick access to relevant information, Dash0 provides two resource views:

• Table view
• Map view

Resources Table View

The resources table supports different views, grouped by service monitoring and infrastructure monitoring.

Service Monitoring includes views of all services and operations with detailed metrics on requests, errors, and durations.

Infrastructure Monitoring includes views for Kubernetes, AWS, and other infrastructure-related resources. The Kubernetes views are structured similarly to the k9s CLI, a popular open source tool for managing Kubernetes clusters.

See how to navigate the Resources table below.

Resources Map View

The resource map shows all services. The connections are automatically extracted from OpenTelemetry signals (Logs, Metrics, Traces).

When hovering over a resource, an overview appears containing high-level information about the service, version, runtime, and health status. When selecting a resource, the sidebar displays more detailed information like request, error, and duration metrics.