Recent changes and improvements to Dash0

Log events in OpenTelemetry are a subset of log records with a special field, EventName, that specifies the type of event it represents. Log events of the same type are supposed to use the same schema for their body.

(Foreshadowing: soon you are going to care a lot about log events in Dash0. Dun dun DUN!)

EventName being a field in OTLP has been an issue: support for OTLP fields is very sparse beyond the Logs API in the SDKs (with notable SDKs not having support to this day) and the OpenTelemetry Collector. Most other logging agents that can send logs over OTLP do not support fields for log records beyond timestamp, body and attributes. And since attributes are generally well supported in the ecosystem, OpenTelemetry Semantic Conventions v1.39.0 introduced otel.event.name as an attribute-level fallback for the EventName field.

In compliance with the semantic conventions, Dash0 now supports otel.event.name as fallback for the EventName field. Log records ingested via OTLP that do not have the EventName field set, are nevertheless treated as log events also when the otel.event.name attribute is present. The same applies to other structured log formats: their logs are similarly handled as log events when the top-level otel.event.name field is set.

Observability is a marathon, not a sprint. While our default dark interface is a favorite for many, we know that lighting conditions and personal preferences vary throughout the day. To give you more flexibility in how you monitor your systems, we’re introducing a Light Mode option for the entire Dash0 UI.

Designed for clarity We’ve carefully adapted our interface to ensure that the transition to a lighter palette feels natural. Every component—from the Service Map to complex trace views—has been refined to maintain the visual hierarchy you're used to. Whether you’re working in a sunlit room or simply prefer a paper-like aesthetic, the new theme provides a clean, focused environment for your data.

What’s new:

• Visual Flexibility — Easily switch between Light and Dark modes to match your surroundings or personal workflow.
• Consistent Semantics — We’ve tuned our color palette so that critical status indicators and OTel metrics remain clear and recognizable against the lighter background.
• Automatic Switching — Set Dash0 to "System" mode to have the UI automatically sync with your OS theme as the day turns into night.

How to switch The fastest way to change your theme is via the Command Menu:

1. Press CMD+KCopy (or CTRL+KCopy) to open the menu.
2. Type "Theme" and select your preferred mode.

Alternatively, you can click on your profile avatar in the sidebar to find the theme selector under your account settings.

The monthly budget limits the total amount due on your invoice across all signal types — spans, logs, metric data points, web events, and synthetic API checks.

Key features

• Advance warnings - Dash0 notifies you at 75% and 90% of your budget via in-app banners and emails to organization admins.
• 4-day grace period - When your budget is reached, telemetry continues to be ingested for 4 days at no additional charge, giving you time to react.
• No data loss - After the grace period, ingestion is paused automatically. Historical data and configuration remain fully accessible.
• Full flexibility - Modify or remove your budget at any time from Settings > Billing & Plans.
  

Prerequisites

You must have the Admin role in your organization. Members without the Admin role cannot view or modify the monthly budget.

To set a monthly budget, navigate to Settings > Billing & Plans and click Set monthly budget in the Next invoice card.

You can find more details in the monthly budget documentation.

The Dash0 CLI enables you to manage your observability assets programmatically, making it easy to version control dashboards, implement GitOps workflows, and automate your observability infrastructure from shell, scripts and agentic AI.

Key features

- GitOps-Ready Asset Management — Create, update, and delete dashboards, check rules, synthetic checks, and views using declarative YAML files. Use the apply command to sync your assets from version control, with support for dry-run validation before making changes.
- Multi-Environment Profiles — Configure multiple profiles for different environments (dev, staging, production) and switch between them seamlessly. Environment variables provide additional flexibility for CI/CD integration.
- Flexible Output Formats — Export assets in table, wide, JSON, or YAML formats for easy scripting, reporting, and backup workflows.

Quick start

# Install via Homebrew
brew tap dash0hq/dash0-cli https://github.com/dash0hq/dash0-cli && brew install dash0hq/dash0-cli/dash0Copy

# Configure your profile
dash0 config profiles create prod \
--api-url https://api.eu-west-1.aws.dash0.com \
--auth-token auth_xxxCopy

# Apply your assets
dash0 apply -f dashboards/Copy

Try it out

The Dash0 CLI is open source and available on https://github.com/dash0hq/dash0-cli. We welcome contributions and feedback from the community.

Let us know which additional features you would like to see!

Press CMD+SHIFT+DCopy to copy to your clipboard a shareable URL with all applied (and supported) feature modifiers. For more flexibility, the chainlink button in the header opens the possibility to configure the URL with the exact parameters you need to bring elsewhere:

Bringing Dash0 closer to where your teams are

Developers work across multiple tools to do their daily work. With Shareable URLs, Dash0 can be integrated with the tools developers are already using, such as internal developer platforms, runbooks, documentation, and communication platforms.

Quick human-readable references to specific Dash0 features have never been simpler.

Help reason through the state of your system and resolve issues faster without needing to hit the browser bookmark. Creating Deeplink URLs for trace and log explorers with custom views, filtered services feature. You can make the developer experience of navigating to a specific setup effortless.

You can find more details in the deeplink's documentation

We've increased the retention period for synthetic API check runs from 30 days to 13 months at no extra cost. This change applies to all check runs executed from January 19, 2026 onwards. Existing check runs will continue to follow the previous 30-day retention policy.

Starting with version 0.99 of the Dash0 Kubernetes Operator, you can define per-namespace settings for exporting telemetry and syncing custom resources (Dash0ViewCopy, Dash0SyntheticCheckCopy, PrometheusRuleCopy, PersesDashboardCopy) to different backends and/or datasets.

The configuration in the Dash0OperatorConfigurationCopy serves as a default that can be overridden by providing an alternative configuration in a namespace's Dash0MonitoringCopy resource.

You can find more details in the operator's documentation.

We've added five new AI integrations to help you build and monitor intelligent applications:

AI Coding Assistants (connect to your Dash0 telemetry):

• OpenCode - Terminal AI coding agent that uses your telemetry data to identify issues and correlate incidents with code changes.
• Kiro - Agentic IDE with spec-driven development that leverages your observability data for telemetry-aware coding and root-cause analysis.

OpenTelemetry Monitoring (observe your AI applications):

• kagent - Kubernetes-native platform for building and deploying AI agents that can connect to MCP servers (including Dash0). Monitor your agents' LLM calls, tool executions, and orchestration flows with built-in OpenTelemetry support.

LLM Application Monitoring (observe your AI applications):

• LangChain - Monitor LLM call performance, token usage, and chain execution flows in your LangChain applications.
• OpenLIT - OpenTelemetry-native observability for LLM applications with automatic instrumentation and GPU monitoring.

These integrations enable you to build AI-powered tools that understand your system's behavior through telemetry, and monitor the performance and costs of your AI applications in production.

Dash0 Folders let you organize assets by service, environment, or business domain, reflecting how your team actually works. This makes it easier to find the right dashboard and keeps your workspace organized as your system evolves.

Folders are built for scale. You can manage them through Infrastructure as Code, keeping your organizational structure consistent across development, staging, and production. Teams can also define which folders appear by default, giving everyone a clean and intentional starting point.

In short: Folders reduce clutter and bring structure to growing observability environments, so Dash0 remains as organized as the systems you monitor.

📊 Service Catalogue

Get a bird’s-eye view of your system health or dive deep into specific code paths.

• The Command Center: A high-level list of every service.
• Infrastructure Resources: See "Failed Checks" on Resources alongside your APM metrics.

Endpoint-Level Granularity: Use the Operations Tab to see which specific operation is failing, even when the rest of the service looks healthy.

🗺️ Service Map

We had a Service Map before so what's new?

• Customizable Views: Save your preferred filters to quickly see the services most relevant to your work by default.
• Dynamic Traffic Visualization: Easily discover traffic flows and paths within your service topology with overlaid particles.
• Grouped External Services: Explore external services organized by similarity, reducing clutter and complexity compared to the full internal map.

We use OpenTelemetry semantic conventions to automatically draw the connection between your services.

• Automatic Discovery: Connections are derived live from your tracing data.
• Visualize the Blast Radius: RED metrics (Requests, Errors, Duration) are overlaid on every connection so you can see exactly where a failure starts and where it spreads.