Dash0
Dash0Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
31 reviews
from
External reviews are not included in the AWS star rating for the product.
Dash0 a observability solutution that saves your time, money and boosts productivity
What do you like best about the product?
Dash0 has enabled us to connect traces, metrics, logs, and business KPIs, making it much easier for our team to monitor and understand how technical data relates to key business indicators.
With this integration, we are now able to analyze traces within minutes and quickly determine whether an error affects a single customer or multiple customers. This capability has been extremely valuable in helping us assess whether an issue requires immediate attention or can be addressed at a later time.
One of the features we value most is the ability to snip out spans on the heatmap, which lets us drill down into traces in just seconds.
We have successfully onboarded three development teams within two to three weeks, and they now use Dash0 on a daily basis.
Most of the effort involved in introducing Dash0 was focused on the initial zero-code instrumentation with Open Telemetry. Dash0 supported us both on-site and through two phone calls, offering recommendations on how to get more out of the solution and how to collect the right Open Telemetry attributes.
Since Dash0 is built on well-defined standards such as PromQL and Perses, the implementation and integration process was straightforward.
With this integration, we are now able to analyze traces within minutes and quickly determine whether an error affects a single customer or multiple customers. This capability has been extremely valuable in helping us assess whether an issue requires immediate attention or can be addressed at a later time.
One of the features we value most is the ability to snip out spans on the heatmap, which lets us drill down into traces in just seconds.
We have successfully onboarded three development teams within two to three weeks, and they now use Dash0 on a daily basis.
Most of the effort involved in introducing Dash0 was focused on the initial zero-code instrumentation with Open Telemetry. Dash0 supported us both on-site and through two phone calls, offering recommendations on how to get more out of the solution and how to collect the right Open Telemetry attributes.
Since Dash0 is built on well-defined standards such as PromQL and Perses, the implementation and integration process was straightforward.
What do you dislike about the product?
Initially, we noticed that some features were missing, such as the ability to define alerts with Terraform. However, this missing feature was implemented a few weeks ago.
What problems is the product solving and how is that benefiting you?
Before we introduced Dash0, we had been running a homegrown observability solution for over five years. After switching to Dash0, we were able to focus more on gathering useful metrics, traces, and logs. The system is now more accessible than ever for every member of the team, which has helped us detect issues earlier—often before we receive any calls about them.
Love the integrations of dash0
What do you like best about the product?
I have used many logging services. The functionality that we mostly use are generally the same. I used dash0 for vercel log drains. Vercel only saves logs for 3 days and we needed longer retention. The integration of dash0 and vercel is really good. Couple of clicks and about 5 minutes all logs from vercel is shown in dash0.
Pros:
1. Seamless integration and superb sdk
2. End to end logging(you can debug an event(api calls) from your frontend to backend)
3. Great customer service
Pros:
1. Seamless integration and superb sdk
2. End to end logging(you can debug an event(api calls) from your frontend to backend)
3. Great customer service
What do you dislike about the product?
The integration was so seamless, I didn't have to dig deeper. No cons for now.
What problems is the product solving and how is that benefiting you?
It is solving my log retention problem.
No Vendor lock in and great cost control
What do you like best about the product?
Dash0 has been very responsive to any questions or concerns I have had. I was able to move all of our monitoring over to it, which has saved me a significant amount of money. The ability to see costs as they occur is a game changer in this field, where you typically only find out what it costs you at the end of the month. They are quick to add new features and have a growing list of integrations, which makes implementation easier.
What do you dislike about the product?
The dashboards are a little limiting, but I get why they are using it as it is open source and can be easily deployed with an app using gitops. However, they connect to Grafana as a prometheus datasource so you can copy the promQL and put in Grafana if needed.
What problems is the product solving and how is that benefiting you?
Dash0 is monitoring our traces and logging allowing us to alert on issues in either area in one place which helps us create a single source of trusth
Reliable, Seamless, and User-Friendly Tool for Start-ups
What do you like best about the product?
Dash0 made our move to OpenTelemetry a lot smoother than we expected. Since it’s OTel-native, the setup was simple and we avoided the vendor lock-in issues we used to run into with legacy tools.
The platform itself is really easy to use. Our engineers don’t have to wrestle with a complicated UI or learn a new query language—they can just dive in, find what they need, and actually get to the root cause of issues faster.
Another big plus: our observability costs have gone down. Pricing is transparent and based on ingestion, so we’re not getting hit with surprise fees or stuck in confusing licensing tiers anymore. All in all, Dash0 has been a solid move for our team
The platform itself is really easy to use. Our engineers don’t have to wrestle with a complicated UI or learn a new query language—they can just dive in, find what they need, and actually get to the root cause of issues faster.
Another big plus: our observability costs have gone down. Pricing is transparent and based on ingestion, so we’re not getting hit with surprise fees or stuck in confusing licensing tiers anymore. All in all, Dash0 has been a solid move for our team
What do you dislike about the product?
There isn’t much to dislike about it. If anything, it could be that some of the documentation could go a bit deeper for advanced use cases. The platform itself works as expected and we didn't have issues with it, but occasionally we’ve had to reach out to support for extra guidance (as we are new). That said, their team has been responsive and very helpful whenever we’ve needed them
What problems is the product solving and how is that benefiting you?
Dash0 helped us make the jump to OpenTelemetry without the headaches. We were stuck with legacy tools that created vendor lock-in and made observability both complicated and expensive. With Dash0’s OTel-native platform, we finally have flexibility and control over our data.
Our engineers can quickly get to the root cause of issues instead of fighting with clunky UIs or query languages, which saves time and reduces frustration. On top of that, the transparent ingestion-based pricing has lowered our observability costs and removed the stress of surprise fees. The result is a faster, more efficient team and a setup that feels built for the long term.
Our engineers can quickly get to the root cause of issues instead of fighting with clunky UIs or query languages, which saves time and reduces frustration. On top of that, the transparent ingestion-based pricing has lowered our observability costs and removed the stress of surprise fees. The result is a faster, more efficient team and a setup that feels built for the long term.
OpenTelemetry-first observability will be the future
What do you like best about the product?
Being OTEL-native means that setup is a breeze. The team are incredibly responsive and helpful. Getting set up was fairly quick as we just added it as a destination in our OTEL collector setup and then removed a load of hackery that was required from using our previous provider. Alerting works well and was easy to integrate with incident.io
What do you dislike about the product?
Some of the out of the box dashboards need improving but the team are working on this. Silencing/muting a particular failing alert check when the alert is parameterized is not supported yet so requires muting the entire alert which is not ideal.
What problems is the product solving and how is that benefiting you?
- Getting visibility in to our running services
- Monitoring for errors and failures
- Monitoring for errors and failures
Easy observability leveraging OpenTelemetry and other open standards
What do you like best about the product?
Dash0 provides great observability on top of OpenTelemtry data. The app provides meaningful and easy to use drilldown features to quickly find problems. To setup Dash0 for a kubernetes cluster can be as simple as installing a helm chart that contains their own operator. This allowed us to quickly get data from our workloads into Dash0. Since Dash0 s built on top of OpenTelemetry, if you are already using this standard it is really easy to switch between products like Dash0 and others that support this open standard. For certain supported runtimes you can also enable auto instrumentation, which will provide some OTel data without the need to change anything in the code / image. Everything is well documented to get you started. We've also experienced great customer support. The people behind Dash0 are really receptive to feedback. We have had some great talks; helping us out with some questions, providing some new feature or configuration options, but also talks about our experience with the current product as well as hearing our thoughts on new ideas that Dash0 had been working on. Different roles within our company have been happy with the Dash0 integration, stating a nice and intuitive UI/UX.
What do you dislike about the product?
Dash0 is quite a new product, so there might be some features that you are used to from the already established observability tools that are not there (yet) in Dash0, but based on our experience with their fast delivery of quality changes, I'm sure that will not be for long.
What problems is the product solving and how is that benefiting you?
All our observability needs are met by using Dash0. We get a nice coupling between logs and traces and with drilldown features we can quickly find problems. Dashboards and alerts are available to help us analyze application metrics.
Worry-Free Observability with Stellar Support
What do you like best about the product?
I found Dash0 super easy to get started with, thanks to their excellent onboarding wizards and detailed getting started documentation. The support and technical team was incredibly engaged, offering extensive office hours to dive into our specific environment. I love that Dash0’s spam filter helps us filter out unnecessary data efficiently, and the pricing model is flat and predictable, unlike other vendors. The platform offers a cohesive user experience with a focus on the observability stack, avoiding the clutter of unnecessary features. The triage function and color coding in the UI are particularly useful for identifying and managing errors.
What do you dislike about the product?
I feel that Dash0 could benefit from having more features. Specifically, the ability to handle business requests or behaviors, allowing users to isolate certain business requests, would be a valuable addition. Additionally, integration with a service catalog like Backstage would significantly enhance its utility for our operations.
What problems is the product solving and how is that benefiting you?
Dash0 simplifies OTEL integration with native support, offers transparent pricing, and effectively filters data noise, enhancing observability. It provides an intuitive user experience and exceptional support, solving my team's data overload and vendor lock-in issues.
Observe OTel signals becomes a piece of cake
What do you like best about the product?
IaC and Kubernetes native integration in conjunction with transparent cost management are superbly designed and documented, and well implemented. This enables governance second to none. The UI is clear and extensive without being cluttered. Customer voice is being heard and features are being implemented in a fast pace and good quality.
What do you dislike about the product?
The product is still missing a few things you would expect from an observability vendor, like trace sampling and SRE patterns. Also the UI is not tailored towards a vast amount of microservices yet.
What problems is the product solving and how is that benefiting you?
Given its seamless OpenTelemetry integration Dash0 it covers basically all signals the standard describes. Furthermore they are very keen on getting the semantics right, such that frameworks and custom integrations can rely on the standard annotations on signals to be interpreted meaningful. This enables us to use it not only for APM, but also correlate logs, have excursions into RUM or simply be alerted when values are out of their thresholds. Even for missing features the openness of the OpenTelemetry architecture allows to route individual use-cases into different products.
Customer-oriented Observability embracing open standards
What do you like best about the product?
Dash0 is built with open industry standards in mind, utilizing OpenTelemetry, Prometheus (OpenMetrics), Perses (Dashboards) and a decent Kubernetes integration to provide tooling that will be familiar for users who heavily invested in rolling their own OSS deployments in the past. Users who are more familiar with vendored solutions should notice very quickly that their hands aren't as limited as they might be used to. In our organisation we know both and love the fact that Dash0 is focused on providing us with the tools that we need. Telemetry data that we don't find useful? Just one click on the Spam button and the unnecessary data will no longer be ingested and cause no additional costs. And the data that we keep? Triage allows me to actually have the system do the correlation across all possible attributes for me. I just need to click on what's interesting. Looking forward to see what comes next.
As an early adopter we sometimes run into questions. So far all of them have been answered promptly and elegantly by the customer support, even in cases where engineering needed to be consulted or when some of our questions resulted in improvement requests.
As an early adopter we sometimes run into questions. So far all of them have been answered promptly and elegantly by the customer support, even in cases where engineering needed to be consulted or when some of our questions resulted in improvement requests.
What do you dislike about the product?
Dash0 is still pretty new, and that does show in feature completeness. The foundation is all there: metric, traces and logs can be stored and queried, displayed on dashboards and used for alerting. But at this point not many value added services are available. Grouping and Triage are great additions, but advanced features like Error Tracking, Synthetics, RUM and SLOs aren't available, yet.
What problems is the product solving and how is that benefiting you?
Dash0 acts as our key APM and general production application observability solution. It is both used by platform teams to monitor the platform and its components and by product teams owning their own applications running on the platform.
As such it is used to determine whether the applications are performing as expected and if they are not, to investigate causes.
As such it is used to determine whether the applications are performing as expected and if they are not, to investigate causes.
Interesting upcoming Observability Tool for OTEL
What do you like best about the product?
Dash0 is a well-structured observability tool built by a team that clearly understands both the technical landscape and customer needs. New features are thoughtfully developed and add meaningful value to the product. The user interface is engineering-focused, making it intuitive and easy to navigate for technical users. Support is responsive, with knowledgeable and helpful engineers providing timely assistance. While we're still in a ramp-up phase, Dash0 has already become an integral part of our daily operations and shows strong potential as a long-term solution.
What do you dislike about the product?
Dash0 shows strong potential, but as it is still in an early stage, it currently doesn’t fulfill all of our needs. That said, the roadmap looks promising and more features are expected to come. For developers who are used to tools like Grafana, adapting to Dash0’s approach to building dashboards requires a bit of a learning curve. However, this adjustment is part of the migration process and should become more natural over time. We're optimistic about its development and look forward to seeing how the product evolves.
What problems is the product solving and how is that benefiting you?
Understand performance bottlenecks of your application and gains insights via logs and traces
showing 1 - 10