Dash0 updates from December 2024

Dash0’s Vercel integration will automatically send all logs from your Vercel workloads to Dash0 for analysis and visualization. Instead of configuring a log drain in Vercel manually, you can just install the integration at https://vercel.com/integrations/dash0 and we do it all for you.

When the integration has been installed, logs from your Vercel projects will be sent automatically to Dash0. This is great news as the log retention within Vercel is only 3 days, while Dash0 offers 30 days of retention for logs and traces. You will also be able to analyze your Vercel logs in context with telemetry from your non-Vercel infrastructure, which makes troubleshooting so much easier.

Additionally, we have integrated the extraction of host and process data from these logs, which is also aligned with OpenTelemetry standards. This improvement significantly enhances your ability to analyze and interpret Journald log data effectively.

OpenTelemetry journald receiver, https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/journaldreceiver

Having good resource attributes on your telemetry is paramount to understanding what is going on in your workloads. Logs, metrics and traces without resource information are basically just data without context. And yet, making sure there are correct Kubernetes resource attributes on all your telemetry is not always easy.

That v0.36 of the Dash0 operator now automatically adds k8s.namespace.name, k8s.pod.name, k8s.pod.uid, and k8s.container.name to all workloads via the Dash0 injector. Under the hood, these attributes are added to the resource attributes sent by your applications via the OTEL_RESOURCE_ATTRIBUTES environment variable. If the workload uses an OpenTelemetry SDK, this environment variable is automatically picked up, and the attributes defined in it are sent along with all the spans, metrics and log records that the application emits.

What's more, the Kubernetes Attributes Processor (which is deployed automatically by the Dash0 operator) will enrich telemetry with a host of other Kubernetes related resource attributes, like the Kubernetes namespace identifier, deployment name and unique identifier, replicaset name and unique identifier etc.

One less thing to worry about, one more thing that just works with Dash0.

Big news: Your workflow, your rules! 🎉 Personalize Dash0 like never before and keep your most-used views just a click away. Dive in and make it yours!

A common problem when creating a dashboard is forgetting to save. Painfully crafted queries and panels are lost. It's so annoying when that happens! No more with Dash0, though!

We even synchronize state across browser tabs for all those tab hoarders! 👀

Some of our users wished to resize the sidebar to allow them to look at a chart with more space. You can now do this. Just drag the edge of the sidebar to where you want it to be!

Logs without a severity aren't nearly as actionable as those stating ERROR or WARN. Explicitly mapping these log levels can be challenging and commonly requires the painful definition of regular expressions.

This capability is currently in closed beta while we validate its effectiveness. Reach out to us to join this closed beta!