
Honeycomb Enterprise
Observability platform has transformed how I trace backend latency and pinpoint API bottlenecks
What is our primary use case?
My main use case for Honeycomb Enterprise is monitoring and troubleshooting performance issues across our backend services and APIs. We use OpenTelemetry to collect traces, and Honeycomb Enterprise helps us track requests across different services to identify latency issues and failures. I mostly use distributed tracing to investigate slow API responses, and BubbleUp is useful for figuring out what is different about requests that are failing or taking longer than expected.
A specific situation where Honeycomb Enterprise helps me solve a problem is when we investigate inconsistent response times in one of our backend APIs. Some requests take much longer than others, but it isn't obvious why. Using distributed tracing, we can see where time is being spent across services. BubbleUp helps us compare slow requests with normal ones and identify patterns related to a particular endpoint and database operation as well. This gives us a much clearer direction for troubleshooting instead of just guessing from the logs.
Apart from my main use case, I mainly use Honeycomb Enterprise to keep an eye on my API latency, error rates, and overall service performance. The query builder is useful when I need to investigate specific endpoints or filter requests by different attributes. I also find the service dependency view helpful for understanding how issues in one service affect others. It is especially useful when logs alone don't give us enough context to identify the root cause. It has made root cause analysis simpler for me and for us.
How has it helped my organization?
I think Honeycomb Enterprise has positively impacted my organization, and the biggest improvement has been in how we approach troubleshooting. Instead of spending a lot of time checking logs across different services, we can use distributed traces to narrow down where an issue is happening. It also makes collaboration easier because developers can look at the same trace and understand what is going wrong. Overall, it has made debugging more structured and helped us identify performance bottlenecks faster, especially in APIs involving multiple services. In this way, it has had a positive impact.
We haven't formally measured the improvement in incident resolution time, so I wouldn't want to give an exact percentage. However, we have definitely noticed that investigating slow APIs and service failures has become faster. Earlier, we had to manually correlate logs across services, whereas now distributed traces and BubbleUp help us narrow down the issue much more quickly. I can't say it has directly reduced outages, but it has made identifying root causes and troubleshooting incidents more efficient. We prefer this approach.
What is most valuable?
The standout features of Honeycomb Enterprise for me are distributed tracing and BubbleUp. Distributed tracing makes it much easier to follow a request across multiple services and pinpoint where latency is coming from. I particularly like BubbleUp because it helps identify patterns in problematic requests without manually checking every attribute. The query builder is also quite flexible, especially when filtering by specific endpoints, response times, or error codes. OpenTelemetry integration is another big plus since it fits well with our existing backend setup.
The biggest advantage of BubbleUp and the query builder in my work is that I don't have to spend as much time manually going through logs. For example, when investigating slow API requests, I can use the query builder to filter by endpoint and look at latency patterns, especially the P95 and P99 response times. BubbleUp then helps compare the slower requests against normal ones and highlight attributes that might explain the difference. This makes troubleshooting more focused because I have a better idea of where to investigate first.
What needs improvement?
One area I'd like to see improved in Honeycomb Enterprise is the learning curve, especially with the query builder. It's powerful, but getting comfortable with complex queries and filters takes some time. BubbleUp is useful, although interpreting the results isn't always straightforward, especially when there are too many attributes. I'd also like better cost visibility and more granular controls over telemetry ingestion since data volume can grow quickly in a microservices environment. More ready-made dashboards and troubleshooting templates would also make onboarding easier for new developers. I think these areas must be improved because newcomers actually struggle.
For how long have I used the solution?
I have been using Honeycomb Enterprise for the past four to five months.
What other advice do I have?
On a scale of 1 to 10, I rate Honeycomb Enterprise around an eight out of 10.
I give it an eight because distributed tracing, BubbleUp, and the flexible query builder are genuinely useful for troubleshooting complex backend issues. OpenTelemetry integration is another big advantage. What holds it back for me is the learning curve, especially for new developers who are new to observability. Better query guidance, more ready-to-use dashboards, and clearer visibility into ingestion costs would push it closer to a nine or 10.
From what I've seen, Honeycomb Enterprise has a solid security foundation, especially with encryption, access controls, and enterprise authentication. For AI features like Canvas and Query Assistant, I think governance is particularly important because they interact with production telemetry. I'd want sensitive request data to be filtered before ingestion and clear visibility into what information AI features can access. Overall, the security approach looks promising, but more transparency around AI data handling and granular access controls would give me greater confidence.
I think the AI capabilities in Honeycomb Enterprise are useful for speeding up investigations, especially when building queries or exploring telemetry data. However, I wouldn't rely on the AI output without verifying it. Sometimes the suggested query might not capture the exact issue I am investigating, particularly when dealing with custom attributes or complex service dependencies. I see it more as an assistant that helps narrow down the investigation rather than something that can reliably identify the root cause on its own. AI helps, but it can't be trusted yet.
We use Honeycomb Enterprise through a public cloud deployment, mainly as a SaaS platform. Our backend services send traces and telemetry data through OpenTelemetry, and Honeycomb Enterprise handles the observability infrastructure. We don't have to manage or maintain the platform ourselves.
Our cloud provider is AWS, and we are using Amazon.
My advice for others looking into using Honeycomb Enterprise is to start with a small set of critical services rather than instrumenting everything at once. Make sure your OpenTelemetry setup is properly configured and that you are capturing useful attributes in your traces. Spend some time learning the query builder and BubbleUp, because that is where a lot of the value of Honeycomb Enterprise comes from. I'd also suggest monitoring telemetry ingestion costs from the beginning, because costs can grow huge. It's a powerful platform, but getting the instrumentation right makes a big difference.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Observability has transformed microservice troubleshooting and now reduces payment flow outages
What is our primary use case?
My main use case for Honeycomb Enterprise is for our customers, who are mostly in e-commerce platforms. They want to understand what an order flow is, what a payment flow is, and how orders are processed.
Honeycomb Enterprise helps with our order flow and payment flow. We started using it for troubleshooting our Microsoft microservices, identifying performance bottlenecks, and analyzing distributed traces, and we thereby aimed to improve production reliability. In e-commerce applications, we have encountered cases where an application normally responds in 200 milliseconds, but suddenly some customers report that requests are taking longer, around five seconds. Without Honeycomb Enterprise, our engineers investigated the API logs, database logs, and infrastructure dashboards separately, and this work extended across many different kinds of people. With Honeycomb Enterprise, engineers filter the slow requests and inspect the distributed traces. They troubleshoot those distributed traces to identify which service is causing the delay.
We are primarily focused on the performance observability of our applications, and we use Honeycomb Enterprise mainly for this purpose.
I can share another scenario as well. Our SaaS platforms serve around 10,000-plus enterprise customers, and sometimes only one customer experiences intermittent failures. With Honeycomb Enterprise, we can query high-cardinality attributes, such as an HTTP response status code greater than or equal to 500. As a result, we understood that we can perform high-cardinality analysis to isolate a small group of requests without separating the dashboards for each different customer. This is one of the functionalities Honeycomb Enterprise specializes in.
How has it helped my organization?
Honeycomb Enterprise has impacted our organization positively. Previously, we relied completely on humans, and the amount of time that we spent on any particular issue was longer. Now we have a better SLA and a faster response time. MTTR has also improved significantly, and we are now primarily focusing on taking the business to the next level, as the majority of our tracing operation is already taken care of by Honeycomb Enterprise. We are primarily focused only on troubleshooting and making fixes for those issues.
Since we started using Honeycomb Enterprise, our resolution time, TTR, has improved by 80%. Productivity has increased by 100% after bringing in this system.
What is most valuable?
I can walk through the best features Honeycomb Enterprise offers one by one. The first is distributed tracing. With distributed tracing, you can track a request across the microservices, from the UI front end to the payment API, and from the payment API to the other back-end databases. For all of these microservices, such as the request service, suggestion service, and payment service, tracking is easier wherever you get an error. That is what distributed tracing means.
The next feature is real-time monitoring. Since ours is an e-commerce platform, we want to monitor each and every request going across the order flow. Analyzing application performance and production incidents is easier because if requests are getting dropped, you can conclude that there is an issue with that system.
Another feature is BubbleUp, which helps with identifying anomalies, and we use it when investigating troubleshooting actions. There are also Service Level Objectives (SLOs), which let you monitor service reliability and performance targets. Service Map is another feature, with which you analyze the map across various different kinds of systems. There is also Enterprise Security for SSO and enterprise access controls, along with some security mechanisms for the same. These are a couple of the features.
The feature that has had the biggest impact on my day-to-day work is real-time monitoring. Our exclusive enterprise support system has a real-time monitoring team, called the Proactive Monitoring team, whose major focus is monitoring these dashboards. When they start monitoring the dashboard and understand that there is an anomaly, an alarm gets picked up. When there is an alarm, we start investigating and debugging, and the issue is resolved in a very proactive manner to overcome any financial loss or business impact.
The AI capabilities of Honeycomb Enterprise have already been implemented in our systems, and I appreciate how intelligently it can detect, investigate, and explain production issues. Speaking first about the AI capabilities, there is Honeycomb Canvas, which uses natural language. We can type in our own language, and it performs AI-assisted telemetry investigation at its end. BubbleUp identifies the attributes that distinguish unusual requests. Ideally, if there is any exclamation or any additional characteristic at the end of a URL, BubbleUp identifies it. Agent Timeline identifies slow LLM calls, tool executions, and agent handoffs, and how they are happening.
Speaking about governance, it is about controlling who can access the system. Honeycomb Enterprise has good governance, and the security is also very great. It can manage the system without any latency or disturbance, and security is the primary factor of the same.
The accuracy and reliability of Honeycomb Enterprise's AI output has brought a major impact to our production environment systems. In terms of accuracy, they do encryption at rest and encryption at the standard. That gives you a security mechanism wherein your data is transferred between various different kinds of systems in a very secure manner. There is also an API authentication mechanism that makes sure your environment-level API keys are always secure. They also follow GDPR and HIPAA. HIPAA is the world’s society standard wherein you need to monitor or maintain data governance, and you need to follow that. They also do penetration testing, which you basically do before deploying anything. On the whole, this is a very good software tool, and I can recommend everyone to use it.
What needs improvement?
Honeycomb Enterprise can be improved in different ways. One area is AI-powered Root Cause Analysis, RCA. The challenge we are currently facing is that engineers often need to investigate traces manually. If Honeycomb Enterprise brought in AI-assisted investigation with some advanced features, it would be even better.
Another area is infrastructure monitoring, which is less comprehensive than that of full-stack competitors. A suggested improvement is to expand its services to Kubernetes infrastructure visibility as well.
The dashboard experience is also an area for improvement. More ready-made dashboards and reusable investigation templates could be brought into the picture because currently, the learning curve for implementing and deploying the dashboards is the biggest challenge.
Also, on the database side, we found that queries process very slowly, and full database diagnostics are not provided. If there were deeper query-level and database performance integrations, it would be better for processing all the queries in real time when troubleshooting database issues faster.
The reason I chose 9 out of 10 is that there is still scope for improvement in root cause investigation. BubbleUp helps identify the patterns behind performance issues, but that is something that needs improvement. The OpenTelemetry integrations also need strong support for open instrumentation standards. The plugins and the integrations should be smarter and faster. Advanced query and event-based analysis requires learning. Cost efficiency is another area, as high telemetry volumes require careful cost management. Full-stack monitoring is also needed and is missing, and some competitors provide better infrastructure monitoring. These are the areas that are lagging, and that is why I marked this as a 9 out of 10.
For how long have I used the solution?
I have been using Honeycomb Enterprise for more than three years. I want to make sure our systems are always stable and working at regular intervals, and that our applications are not going down at any point in time.
What's my experience with pricing, setup cost, and licensing?
We purchased Honeycomb Enterprise through the AWS Marketplace.
What other advice do I have?
On a scale of 1 to 10, I would rate Honeycomb Enterprise overall a 9 out of 10.
I would recommend considering Honeycomb Enterprise definitely if you are an organization running complex microservices, specifically cloud-native applications and distributed systems, especially when the main challenge is identifying and resolving production issues. There are several things to check before buying.
The first is your organization. You need to determine whether your business requirements really call for it, and whether your organization is small-scale, medium-scale, or large-scale. You also need to consider whether you are looking for AI capabilities, security, governance, and integration.
You also need to evaluate the pricing, because the pricing is based on the event ingestion volume. As the number of events increases, your price also increases. You need to consider your retention requirement, meaning how many days you want to store the data.
You also need to understand what kind of support you need from Honeycomb Enterprise. Make sure you understand that part well. You need to consider enterprise support, SLAs, onboarding assistance if you need it, and any escalation procedures. All of these things need to be taken into consideration before making any purchase.
For me, I would say mid-scale and large-scale enterprises can definitely try utilizing it. For small-scale enterprises, I do not think this is the preferred tool.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Observability has transformed how my team pinpoints bottlenecks and resolves production issues
What is our primary use case?
My main use case for Honeycomb Enterprise is application observability and troubleshooting distributed systems, where I analyze traces, investigate latency and errors, understand service dependencies, and identify performance bottlenecks. Its high cardinality views help me narrow down issues quickly and understand what is happening across different services, making production debugging more efficient.
One specific example of how I've used Honeycomb Enterprise to solve a problem is when troubleshooting a slow API in a distributed application. I examined traces across multiple services and identified where the latency was occurring, which helped narrow the issue down to a slower database call rather than the API itself. This made troubleshooting faster and helped my team focus on the actual bottleneck instead of investigating every service individually.
What is most valuable?
The best features that Honeycomb Enterprise offers include distributed tracing, high cardinality querying, real-time observability, service dependency analysis, trigger-based alerts, and collaborative debugging.
The feature I find myself using the most is high cardinality querying combined with distributed tracing, as it helps me pinpoint the root cause of production issues much faster.
By using Honeycomb Enterprise, I have gained a crystal clear idea of the infrastructure that is behind our applications, also improving my application observability and troubleshooting process. It makes it easier for me to identify performance bottlenecks, trace errors across distributed services, and investigate production issues, reducing manual debugging effort, improving collaboration between the development and infrastructure teams, and helping us make faster and more informed decisions.
There is less manual effort and faster resolution time, with the biggest improvement being faster troubleshooting and reduced manual efforts. Instead of checking multiple services and logs individually, I use distributed traces to narrow down the source of an issue, helping the team identify bottlenecks more quickly and reducing investigation time. While I don't have verified percentage-based metrics, the improvement in debugging efficiency and incidents visibility has been valuable.
What needs improvement?
Honeycomb Enterprise is already good, and I would like to see more out-of-the-box integrations, such as simpler dashboards, customization, and more flexible alert configurations. Improvements in query performance for very large datasets and clear cost and usage visibility will also make the platform even more useful.
For how long have I used the solution?
I have been using Honeycomb Enterprise for the last six to seven months.
What do I think about the stability of the solution?
Honeycomb Enterprise is stable.
What do I think about the scalability of the solution?
The scalability is also good, providing me access to the platform whenever needed. It offers good scalability for distributed applications and growing telemetry volumes, handling high cardinality events and traces across multiple services, making it useful as application workloads grow. I particularly appreciate that teams can expand observability without managing the underlying storage and infrastructure. However, data volume retention requirements and usage costs should be monitored as the environment scales.
How are customer service and support?
The customer support is good, but we did not get a chance to connect with them.
Which solution did I use previously and why did I switch?
We were using different types of solutions, relying more on traditional logging and monitoring tools such as CloudWatch and basic log analysis. We considered Honeycomb Enterprise because we needed deeper distributed tracing, high cardinality queries, and better visibility across services, making root cause analysis more efficient, especially when troubleshooting complex application issues.
How was the initial setup?
The setup process is easy with no significant challenges. We start by creating a Honeycomb Enterprise environment, configuring API keys, and instrumenting the application using OpenTelemetry. Then, we configure telemetry collection, define datasets, and set up dashboards and alerts. Once the data starts flowing, I validate traces and monitor application performance. The main effort is usually in instrumentation and deciding which telemetry data is most useful to collect.
What was our ROI?
The main return on investment is operational efficiency with Honeycomb Enterprise helping me reduce manual troubleshooting by making it easier to identify root causes across distributed services. It helps engineers spend less time investigating logs and more time resolving issues. While I don't have verified financial figures or exact percentages, the visibility provided offers clear operational value.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, I think the pricing is minimal. The main consideration regarding pricing is data volume and usage, and the setup is relatively straightforward.
Which other solutions did I evaluate?
Before moving to Honeycomb Enterprise, we previously used AWS CloudWatch and traditional log monitoring tools, considering Honeycomb Enterprise for its advanced distributed tracing, high cardinality querying, and better visibility across microservices. It makes root cause analysis faster and simplifies troubleshooting complex production issues.
What other advice do I have?
I would rate Honeycomb Enterprise an eight out of ten.
I chose eight out of ten because Honeycomb Enterprise provides strong observability, powerful distributed tracing, and effective debugging capabilities, helping teams identify performance bottlenecks and troubleshoot production issues faster.
Regarding governance and security, I believe they are important when using AI for application observability. Data privacy, access controls, and clear audit trails should be maintained, especially when telemetry may contain sensitive information. AI-generated insights should be transparent and validated by engineers before taking action, with human oversight and proper data handling policies being essential for building trust in the platform.
In terms of accuracy and reliability, Honeycomb Enterprise's AI-driven insights can be useful for identifying unusual patterns, investigating errors, and understanding performance issues. I find the output most valuable when it is supported by actual traces and telemetry data, and I will still validate AI-generated recommendations before making production changes. Accuracy, consistency, and explainability are important for reliable troubleshooting.
Currently, I am using Honeycomb Enterprise in a public cloud as a SaaS-based product, where application telemetry including traces, events, and performance data is sent to Honeycomb Enterprise through instrumentation and OpenTelemetry. This allows my teams to monitor distributed applications without managing the observability infrastructure themselves.
The advice I would like to give is to recommend starting with OpenTelemetry instrumentation and identifying the most critical application workflows to monitor. Make sure to evaluate distributed tracing, high cardinality during alerting, and integration with your existing tools. Start with a small proof of concept, monitor telemetry costs, and gradually expand coverage. The biggest value comes from using the data to identify root causes rather than simply collecting more logs.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Observability has improved debugging speed and now helps trace complex user-specific issues
What is our primary use case?
Over the last three years, I have been using Honeycomb Enterprise primarily for application monitoring and troubleshooting. The main use case is application monitoring and troubleshooting. When an application experiences performance issues or unexpected errors, Honeycomb helps trace requests across different services and identify where the problem is occurring. This makes debugging easier and helps developers understand the root cause instead of just examining error logs.
For example, when an API request takes longer than expected, I use Honeycomb to trace a request and see which part of the process is causing the delay. Looking at the timing across different services helps narrow down the bottleneck and makes it easier to fix the issue.
Another useful scenario for my main use case with Honeycomb Enterprise is investigating issues that happen only for certain users or under specific conditions. Honeycomb helps explore the application's details, spot unusual patterns, and narrow down the cause. This is especially valuable when working with complex applications where the problem is not easy to reproduce locally.
How has it helped my organization?
Honeycomb Enterprise is extremely helpful for my organization. The biggest potential benefit is faster troubleshooting and better visibility into the application's performance. It helps developers understand where the issue is happening instead of spending too much time guessing locally. This can make debugging more efficient and help the team focus on delivering improvements rather than investigating the same problems repeatedly.
I do not have an exact metric to share, but the better visibility into traces and the application's behavior can help developers narrow down issues faster. It can reduce the time spent checking logs manually and make troubleshooting more focused. The actual improvements depend on the applications and how well the telemetry is configured.
What is most valuable?
The best features that Honeycomb Enterprise offers, which I find most valuable, are distributed tracking, powerful querying, and high-cardinality data analysis. I especially appreciate the ability to filter telemetry by specific details such as user ID or request type to narrow down an issue quickly. OpenTelemetry support is also useful because it helps integrate observability into existing applications.
Distributed tracing makes troubleshooting easier for me because I can follow a request across different services and see where the delay or an error occurs. Instead of checking each service separately, I can narrow down the problem faster. High-cardinality queries are also useful for finding issues affecting specific users or requests, which helps make debugging more focused and efficient.
One aspect I appreciate about the features is the flexibility to analyze telemetry data from different angles without knowing the exact cause of an issue. In development, problems do not always follow a clear pattern, so being able to investigate unexpected behavior is really useful. OpenTelemetry support is another practical benefit because it works well with modern application stacks.
What needs improvement?
Honeycomb Enterprise needs some changes to be improved. I think setup instructions and understanding queries can take some time, especially for developers who are new to observability. More practical examples, a simpler setup guide, and clear cost visibility would make it easier for teams to get started.
I believe the interface could make common troubleshooting tasks easier for new users, with clearer navigation and more useful query examples. Better documentation with real-world scenarios would also help developers understand how to investigate issues step-by-step. Clear guidance on telemetry usage and cost would be another useful improvement.
For how long have I used the solution?
I have been using Honeycomb Enterprise for the last three years.
What do I think about the stability of the solution?
Honeycomb Enterprise is stable.
What do I think about the scalability of the solution?
Honeycomb's scalability is good for growing applications and large volumes of telemetry, making it useful as the system becomes more complex.
How are customer service and support?
The customer support experience seems good overall, and the clear documentation is helpful when troubleshooting technical issues. I would rate the customer support as an eight.
Which solution did I use previously and why did I switch?
Previously, I used traditional logging and monitoring tools to investigate application issues.
What was our ROI?
The main potential return on investment is time saved during troubleshooting. By tracing requests and identifying bottlenecks faster, developers can spend less time investigating issues manually and more time on development. I do not have verified figures for the cost savings on time reduction, but this is where I see the biggest value.
What's my experience with pricing, setup cost, and licensing?
The pricing and setup for Honeycomb Enterprise are fairly straightforward, but pricing depends on the amount of telemetry data and the plan I choose. I would recommend monitoring data usage carefully to keep costs under control as the application grows.
Which other solutions did I evaluate?
Before choosing Honeycomb Enterprise, I considered DataDog and New Relic. I compared their observability features, integration, and pricing.
What other advice do I have?
I give Honeycomb Enterprise an eight.
I chose eight because Honeycomb offers powerful troubleshooting and observability features, especially distributed tracing and flexible querying. These capabilities can help developers find the root cause of issues more efficiently. I left room for improvement in onboarding, ease of use for beginners, and cost visibility.
Regarding governance and security, I think security and data privacy are very important when using AI for observability. Teams need clear access controls and confidence that sensitive application data is handled properly. I would also want transparency about how AI uses telemetry data and how organizations can control access to it.
For its capabilities, accuracy, and reliability, AI can be useful for summarizing telemetry and pointing developers toward the possible cause of an issue. However, I would not rely on its output blindly. I would still check the underlying traces and data before making changes, especially when investigating production issues. For me, AI is most useful when it speeds up the investigation while keeping developers in control.
Honeycomb Enterprise is available as a cloud-based observability platform, which means teams can send application telemetry to it without managing the observability infrastructure themselves.
Honeycomb can work with telemetry from applications running on platforms like AWS, Azure, and Google Cloud. This depends on my organization's existing infrastructure.
I recommend Honeycomb for teams that need better visibility into application performance. Start with a small setup, explore distributed tracing, and monitor data usage to keep costs under control.
Observability has improved troubleshooting speed but still needs a gentler learning curve
What is our primary use case?
Honeycomb Enterprise serves as the main observability, distributed tracing, and troubleshooting solution for microservices in my project.
A specific example of how I have used Honeycomb Enterprise in a real scenario involved an API that was taking longer than expected. In my day-to-day work, apart from troubleshooting, I also use Honeycomb Enterprise to monitor application performance after deployments and check whether response times or error rates have changed.
How has it helped my organization?
Honeycomb Enterprise has positively impacted my organization by enabling troubleshooting and production monitoring in a more efficient way.
Honeycomb Enterprise has helped make troubleshooting more efficient by reducing the time spent manually checking logs across multiple services.
What is most valuable?
The best features Honeycomb Enterprise offers are the distributed tracking, flexible querying, and the ability to analyze high-cardinality data.
Flexible querying in Honeycomb Enterprise helps me investigate issues without being limited to predefined dashboards.
Another thing I appreciate about Honeycomb Enterprise is that I can connect the dots between different services instead of looking at each solution in isolation.
What needs improvement?
Honeycomb Enterprise can be easier to learn, especially for those who are not familiar with distributed tracing and high-cardinality data.
For how long have I used the solution?
I have been using Honeycomb Enterprise for about two years.
What do I think about the stability of the solution?
Honeycomb Enterprise is stable and provides useful visibility into application behavior, helping my team investigate performance issues across services.
What do I think about the scalability of the solution?
Honeycomb Enterprise offers good scalability for monitoring applications with multiple services and large volumes of telemetry data.
How are customer service and support?
The customer support for Honeycomb Enterprise is good. I would rate the customer support seven out of ten.
What was our ROI?
I definitely see a return on investment in terms of time saved with Honeycomb Enterprise.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, setup cost, and licensing, these are not much of a concern because as the volume of telemetry data increases, pricing will be a consideration. However, the initial setup is fairly straightforward.
What other advice do I have?
I would rate Honeycomb Enterprise seven out of ten. The reason I gave this rating is because it provides strong distributed tracing and useful query capability, but the learning curve is steep for new users.
Regarding Honeycomb Enterprise's AI capabilities, I find it a useful foundation for troubleshooting, but I would want clear controls around data access and user permissions. Honeycomb Enterprise's AI output is sometimes useful but may not always meet my expectations for accuracy and reliability.
I find Honeycomb Enterprise's AI output accurate. I find Honeycomb Enterprise useful for understanding issues across services, but I treat AI analysis as a recommendation rather than the final answer.
My advice would be to clearly identify your observability needs before adopting Honeycomb Enterprise and ensure the team is comfortable with distributed tracing and OpenTelemetry.
Deep tracing has improved microservice visibility and now reduces API bottlenecks faster
What is our primary use case?
A typical example of how I have used Honeycomb Enterprise to troubleshoot is with slow payment processing APIs, where Honeycomb Enterprise's distributed tracing helps identify whether the delay comes from a database query, an external payment gateway, or communication between microservices.
Another important use case is improving visibility across distributed services, which helps teams identify recurring errors and monitor API performance while reducing troubleshooting time.
How has it helped my organization?
I have not established exact metrics to share, but the main improvement I would highlight is reduced mean time to resolution, faster identification of API bottlenecks, fewer recurring production incidents, and improved service reliability.
What is most valuable?
I have covered most of the valuable features I use from Honeycomb Enterprise, which include distributed tracing, the BubbleUp features, the service maps, and SLO monitoring.
What needs improvement?
The alert management system of Honeycomb Enterprise could be improved with more flexible alert configurations and better integration with existing monitoring tools being potentially helpful.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Which solution did I use previously and why did I switch?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
Regarding Honeycomb Enterprise's AI capabilities, it offers a solid foundation for security and governance, particularly through role-based access controls, single sign-ons, and data access management. For its AI capabilities, better transparency into how AI processes data, stronger audits, and more controls over sensitive information would be very valuable.
The AI capabilities of Honeycomb Enterprise seem quite promising for identifying anomalies, analyzing performance, and suggesting potential root cause analyses, but accuracy and reliability are critical, especially in complex microservices environments, where AI-generated insights should be validated against actual traces and data to avoid false positives or misleading conclusions.
I recommend starting with a small set of microservices at first and then gradually expanding to other microservices, while investing time in proper implementation, defining clear SLOs, configuring meaningful alerts, monitoring ingestion costs, and using sampling strategies where appropriate, as Honeycomb Enterprise is particularly valuable for complex distributed systems needing deep visibility into application performance. My overall rating for Honeycomb Enterprise is eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Observability has transformed incident resolution and now helps teams pinpoint issues faster
What is our primary use case?
My main use case for Honeycomb Enterprise is application observability and troubleshooting distributed applications. When it comes to scalability and handling applications, managing microservice-architected applications is quite difficult. There should be a trace of each log and observability point. Honeycomb Enterprise helps us follow requests across multiple different services and investigate latency and errors, understanding where the problem originates, which ordinary logs and infrastructure generally do not provide with sufficient context.
For example, if I consider one API that becomes very slow after a software release, I find that the infrastructure metrics show normal CPU and memory usage, but what our customers experience is delay in getting back the response. Honeycomb Enterprise helps me examine the request trace across the API, the downstream services, and the database calls to identify the slow operation and investigate the root cause.
How has it helped my organization?
Honeycomb Enterprise has positively impacted my organization by reducing the time engineers spend investigating production incidents and reducing customer resolution time. We reduce troubleshooting time for complex issues by 40 to 50%. These improvements are very important when handling things in production.
I measure that 40 to 50% reduction in resolution time by estimating improvements on issues that previously took one to two hours to isolate, which can often be narrowed down to 20 to 30 minutes using distributed tracing and BubbleUp. The end-to-end tracing follows requests across multiple microservices instead of manually correlating logs from each service. Using high-cardinality queries, we filter request ID, endpoint, service, and other attributes to isolate affected requests and perform faster root cause analysis, where engineers could narrow down the problematic service or database call, significantly reducing investigation time. Previously, investigations taking two hours can now be completed in 30 minutes to one hour, resulting in a 50% reduction.
What is most valuable?
One of the best features I appreciate most about Honeycomb Enterprise is the distributed tracing capability, because it is one of the most valuable capabilities, helping me understand how an individual request passes through different services and identify where time is being spent, allowing me to easily narrow down the source of an error. The high-cardinality queries are also very useful because I can investigate specific users, requests, services, or error conditions without depending entirely on predefined dashboards.
The high-cardinality analytic tools help me in my day-to-day work by allowing me to investigate issues at a much more granular level. I considered an issue particularly with an API request, where it became slow and customers experienced delayed response. We could filter the telemetry using attributes such as the request ID, user ID, endpoint, service name, and deployment versions to identify the specific request or service causing the issue. Instead of relying only on a general dashboard to search through logs, we could drill into distributed traces and identify where latency or errors occurred. This helps speed up root cause analysis, reduce troubleshooting effort, and improve incident resolution.
What needs improvement?
I suggest a few areas where Honeycomb Enterprise could improve. One is better onboarding for OpenTelemetry and more customizable dashboards, clearer cost forecasting, and stronger integrations with DevOps and incident management workflows. These improvements would make the platform easier to adopt while preserving its strength in detailed production investigations.
For how long have I used the solution?
I have been using Honeycomb Enterprise for the past two years.
What other advice do I have?
I rate Honeycomb Enterprise an eight overall.
I rate it an eight because the main strengths are distributed tracing, flexible investigation, and the potential to reduce debugging time. The deductions reflect the learning curve. I deduct two points because dashboard customization has limitations, onboarding for OpenTelemetry needs improvement, and clear cost forecasting is required. Additionally, I would appreciate stronger integration with DevOps and other incident management workflows.
Regarding Honeycomb Enterprise's governance and security, it is very important for an organization because governance should cover access controls, SSO (single sign-on) operations, role-based permissions, telemetry retention, and the handling of sensitive attributes. Honeycomb offers enterprise-oriented access and security capabilities, but the exact controls depend on the plan and configurations. They are well-versed in security protocols, but we have to ensure that we are not sending secrets or unnecessary personal data in traces and verify the organization's compliance requirements before onboarding production telemetry.
Regarding Honeycomb Enterprise's accuracy and reliability of output, the platform provides useful request-level context for troubleshooting when telemetry is correctly instrumented and collected. Its findings have really helped my engineers and me identify bottlenecks. However, data still needs interpretation in context and verification against application behavior. Missing instrumentation, sampling, and incomplete attributes can limit investigation, but overall, Honeycomb Enterprise is accurate and reliable, cutting down 50 to 60% of the troubleshooting time.
When advising others looking into using Honeycomb Enterprise, I recommend that when starting with critical applications or microservices, troubleshooting production issues is very important and time-consuming. There will be a number of services, and tracing in and out of each service is very challenging. I suggest integrating with OpenTelemetry, instrumenting important services and APIs, and using distributed tracing and high-cardinality queries to understand where requests are slowing down or failing. Others can assess their requirements and research the features they seek. Training is involved for the engineering team on tracers and queries capabilities, which requires considerable effort, and saving this effort is something I highlight as vital. My rating for this product is eight out of ten.
Observability has transformed how I troubleshoot complex production issues and resolve incidents faster
What is our primary use case?
My primary use case for Honeycomb Enterprise is troubleshooting production applications and distributed services using the observability data, particularly when a normal log search is not enough to explain what is happening.
A specific example where Honeycomb Enterprise helped me troubleshoot is in investigating a slow or failed API request, where the request goes from client to load balancer, then API gateway, then service A, service B, and finally a database in a multi-layer application.
I am using Honeycomb Enterprise in this way only.
What is most valuable?
Some of the best features Honeycomb Enterprise offers include distributed tracing, which is probably the most important feature for my use case, and it helped me answer where the request spent its time.
Honeycomb Enterprise has positively impacted my organization by improving the way I understand production problems and significantly reducing the time required to do so. I estimate that I spend around 40% less time troubleshooting now compared to before using Honeycomb Enterprise.
What needs improvement?
The learning curve for things such as traces, spans, high-cardinality data, and advanced queries is an area where Honeycomb Enterprise can be improved.
I would rate Honeycomb Enterprise around 8.5 out of 10 because being able to investigate a specific production request and understand what happened across a distributed system provides a very different value from simply watching CPU, memory, and uptime dashboards.
For how long have I used the solution?
I have been using Honeycomb Enterprise for around one and a half years.
What do I think about the stability of the solution?
Honeycomb Enterprise is stable.
What do I think about the scalability of the solution?
Honeycomb Enterprise is highly scalable.
How are customer service and support?
The customer support for Honeycomb Enterprise is good.
I would rate the customer support for Honeycomb Enterprise nine out of 10.
Which solution did I use previously and why did I switch?
I have not used any solution before this.
How was the initial setup?
I have mentioned several things that need improvement for Honeycomb Enterprise.
What about the implementation team?
I did not purchase Honeycomb Enterprise through the AWS Marketplace.
What was our ROI?
I have seen a return on investment with Honeycomb Enterprise, as I mentioned, with 40% time saved in troubleshooting.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Honeycomb Enterprise is that this is an area I evaluate carefully due to potentially complicated observability pricing as the amount of telemetry grows with application traffic.
Which other solutions did I evaluate?
Before choosing Honeycomb Enterprise, I evaluated other options such as traditional ones like CloudWatch, Grafana, Prometheus, New Relic, and Datadog.
What other advice do I have?
Some of the best features Honeycomb Enterprise offers include distributed tracing, which is probably the most important feature for my use case, and it helped me answer where the request spent its time.
If production troubleshooting is an issue for you, Honeycomb Enterprise is the only solution and is a very good one. I would rate this review 8.5 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Tracing billions of events has become faster and observability now simplifies root-cause analysis
What is our primary use case?
I joined Smarsh in 2023 as a software engineer, and from that point until last year, we were using Honeycomb Enterprise. Recently, we migrated to a different service.
I have used Honeycomb Enterprise in the past 12 months, and it was very good. We used it mainly for tracing and observability. By observability, I mean we did not use it primarily for metrics and other features. The main goal was to use it for tracing, traceability, and debugging errors.
When comparing Honeycomb Enterprise to DataDog, the current service we are using has the best features. However, I never explored metrics completely with Honeycomb Enterprise. With tracing, Honeycomb Enterprise is the cheaper and best service for tracing and traceability compared to DataDog. I did not explore Honeycomb Enterprise to that extent for metrics.
What is most valuable?
The best feature Honeycomb Enterprise provides is the sampling. Whenever we publish traces, out of 1000 traces, it samples the best-rate traces, and it has the capability to implement a graph from the tracing that we have published. This is the most impressive feature I have seen. From error logs or whatever we publish, we can easily visualize those traces in graphs and identify the number of occurrences that have happened for a particular trace, error log, or observability failure in a service. The main features I highlight are the graph feature and sampling.
With structured tracing, it helps us understand complex user interactions. Since we are dealing with billions of traces every day from 1000 or 2000 services running daily, with each service emitting nearly more than 10,000 traces, identifying which service has errored out in a particular environment or region and at what time was critical. Honeycomb Enterprise is the best solution for this. It performs sampling based on error rates and provides us the data to visualize. When we search for any error logs or what happened with a service at a particular moment, it is very easy to search any traces and identify the root cause and fix those issues. Using Honeycomb Enterprise as a tracing service made it very quick to identify and fix issues.
When assessing the impact of high cardinality data analysis on application performance optimization, our company deals with multiple documents, and each data point deals with multiple documents, multiple IDs, and multiple unique records. Each record has a high cardinality field. If we go with any observability services like DataDog, Grafana, or other services, publishing high cardinality fields would be difficult for the system and would cost more. Honeycomb Enterprise supports high cardinality fields in a very easy way, and the pricing is very reasonable. We used to publish even high cardinality fields for tracing, but not for metrics.
What needs improvement?
The areas for improvement with Honeycomb Enterprise lie in the query UI, which could be improved to a more current standard. The older query interface shows facets, and if I need to select an option, I must drop down through multiple choices, which could be improved substantially, and we could even adopt AI tooling. While performing sampling, I do not know internally how Honeycomb Enterprise executes the sampling. At the very least, while querying, as an external user or someone who does not know how the code works for their service, the experience could be better. Let me illustrate: I know my service code and how it works, but another team member may not completely understand how the code works. Even if they search in Honeycomb Enterprise, they need to understand what traces we are publishing. If AI implementation were added, it could suggest queries or, when I type something like "I want these traces present within this time in this service," it should frame the query automatically. I want that feature to come to Honeycomb Enterprise. I do not know whether it exists currently because we stopped using Honeycomb Enterprise almost five or six months ago.
What do I think about the stability of the solution?
For stability, I can rate it a nine or ten. I have never seen Honeycomb Enterprise go down.
What do I think about the scalability of the solution?
Regarding scalability, I have never seen any lagging in the service while using it, and I have never seen Honeycomb Enterprise go down. Since it is a managed service, I agree that it was scalable. I would rate this a nine as well.
How are customer service and support?
For technical support, I never had to make a call for any support. Our concern was not to maintain Honeycomb Enterprise. As an engineer, we simply utilized that tool. We were never concerned about how it connects, what it does, what the storage was, or what billing had been done for it.
Which solution did I use previously and why did I switch?
If comparing Honeycomb Enterprise to DataDog, the current service we are using has the best features. However, I never explored metrics completely with Honeycomb Enterprise. With tracing, Honeycomb Enterprise is the cheaper and best service for tracing and traceability compared to DataDog. I did not explore Honeycomb Enterprise to that extent for metrics.
How was the initial setup?
Since Honeycomb Enterprise is not self-hosted and is a managed service, we never maintained anything.
Which other solutions did I evaluate?
We used Honeycomb Enterprise mainly for tracing and observability. By observability, I mean we did not use it primarily for metrics and other features. The main goal was to use it for tracing, traceability, and debugging errors.
What other advice do I have?
I would recommend Honeycomb Enterprise based on cost evaluation. Companies considering purchasing it should discuss the features they want and partner with Honeycomb Enterprise. The decision is theirs, but as an end-user, I would recommend the UI interface, the interaction with the UI, and all the services that I have seen in Honeycomb Enterprise.
I am completely unaware of the pricing because we as engineers are not aware of the price. In every company, there is a pricing manager, COGS management team, and a fabric team. The fabric team handles all the pricing models and related matters. As an end developer, I am not certain what pricing was incurred by Smarsh for using this service. However, one thing I learned is that due to pricing considerations, Smarsh moved from Honeycomb Enterprise to another service.
I would rate this review an eight overall.
Observability has transformed how I troubleshoot microservices and reduce incident time
What is our primary use case?
I have been using Honeycomb Enterprise for the past three years. My main use case has been troubleshooting and performing monitoring for Kubernetes-based applications and microservices.
How has it helped my organization?
Honeycomb Enterprise has had a very positive impact on our organization by reducing the time it takes to identify and resolve production issues. Instead of spending hours searching through logs across multiple Kubernetes services, we can quickly pinpoint the source of the problem using distributed tracing. This has really improved our mean time to resolution and reduced downtime while helping us deliver a more reliable experience for our users. It also gives the engineering team greater confidence when deploying a new release because we can validate performance and catch regressions much earlier.
What is most valuable?
When I observed a significantly increased response time after a new release to one of our microservices running on AKS, the infrastructure appeared healthy and the CPU and memory were normal, but users were reporting latency delays. Using Honeycomb Enterprise, I filtered traces for those affected services and compared slow requests against normal ones. The distributed trace showed that most of the latency was coming from a downstream API call rather than the application itself. By drilling into the trace attributes, I was able to identify that a specific endpoint was experiencing significantly high response time. After the deployment, I rolled back the change and confirmed the latency returned to normal, then fixed the issue before redeploying. Honeycomb Enterprise made it very easy for me to pinpoint the exact service and operation causing the slowdown, which reduced our troubleshooting time very significantly.
Beyond troubleshooting production issues, I have also used Honeycomb Enterprise proactively for monitoring and validating deployments. After a new release, I monitor key metrics such as request latencies, error rates, and throughput to ensure there are no regressions. I have also used it during root cause analysis by correlating traces across multiple Kubernetes services, which helped determine whether an issue originated in the application, the infrastructure, or an external dependency. The ability to query high-volume issues data and drill into specific requests has been specifically valuable for identifying all these issues and reducing troubleshooting time. Overall, it has become an important part of our observability workflow and helps solve incidents much faster.
Some of the best features for me include distributed tracing, which gives me end-to-end visibility into a request as it flows across multiple microservices, making troubleshooting faster. I really appreciate the ability to query high-level data without having to predefine dashboards or indexes. This means I can investigate issues from different angles even if I did not anticipate them beforehand. Another feature I use frequently is BubbleUp, which automatically highlights the differences between normal and problematic issues, making it easier to identify root cause. The integration with OpenTelemetry is a significant advantage because it allows us to collect standardized telemetry from our Kubernetes workflows and workloads without being locked into a proprietary instrumentation approach.
What needs improvement?
Overall, I have had a very good experience with Honeycomb Enterprise, but there are a few areas where it could be improved. I would like to see more out-of-the-box dashboards and templates for common Kubernetes and cloud-native workloads so that new users can get value more quickly. The learning curve can be steep, especially for engineers who are new to distributed tracing and observability concepts. Additionally, while the query capabilities are very powerful, there are times when specifying advanced query workflows could be improved to provide a better overall experience for troubleshooting and observability.
Beyond what I mentioned, there are a few other areas that could also be improved. I would like to see even deeper native integration with more DevOps and ITSM tools to make it easier to connect observability data directly into incident management and operational workflows. Regarding pricing, Honeycomb Enterprise delivers strong value, but as organizations scale and generate larger volumes of telemetry, cost can become a consideration. More flexible pricing options or cost optimization features for high-volume environments would be helpful. My support experience has been generally positive, but faster turnaround time for complex technical issues and more advanced implementation guides or best practices documentation would make onboarding and troubleshooting easier. These improvements would make an already strong observability platform even more accessible and scalable for enterprise teams.
For how long have I used the solution?
I have been working in my current role for the past almost three years. In general, working as a technology engineer, I have been in the technology market for a span of ten good years.
What do I think about the scalability of the solution?
I would rate the scalability as very good. As our Kubernetes environment and the number of microservices grew, Honeycomb Enterprise continued to handle the increased telemetry volumes without requiring major changes on our side because it is a managed SaaS platform. We were able to onboard additional services and workloads with minimal effort using OpenTelemetry. The main consideration is managing telemetry volume as your environment scales since more data can impact cost. As long as you have good instrumentation practices and data management policies, the platform scales very well for enterprise environments.
How are customer service and support?
Overall, my experience with Honeycomb Enterprise customer support has been positive. The support team has been knowledgeable and responsive, especially when we had questions about instrumentation, OpenTelemetry integration, or troubleshooting complex observability issues. For standard questions, we usually receive helpful responses within a reasonable time frame. For more complex technical issues, resolutions sometimes take longer because they require deeper investigation, but the support team kept us informed throughout the process. I rate the support around 8 to 9 out of 10. The main area for improvement would be faster turnaround time for complex enterprise cases and more advanced technical documentation for edge case scenarios.
Which solution did I use previously and why did I switch?
The organization was actually using a different solution before I came in. I do not know the reason why the organization changed, so I cannot provide more insight into that.
How was the initial setup?
The pricing is reasonable for the value it provides, especially for organizations running large-scale microservices. The biggest consideration is that cost can increase as telemetry volume grows. It is important to have very good data management and retention policies in place. From a setup perspective, the initial implementation was straightforward since we use OpenTelemetry with our Kubernetes environment and the documentation made the onboarding process fairly smooth. The licensing was also relatively simple to manage. My only suggestion would be to offer more flexibility for organizations with rapidly growing telemetry volume or response spikes in usage. Overall, I am very satisfied with the setup experience and the licensing, and I felt the platform delivered good value for the investment.
What was our ROI?
We did not publish a formal KPI specifically for Honeycomb Enterprise. From my experience, I estimate our incident investigation time dropped by around 40 to 50 percent for complex microservice issues. Problems that would previously take one or two hours to isolate were often narrowed down to 20 to 30 minutes using distributed tracing or BubbleUp. This translates into faster incident resolution, less service disruption, and quick recovery during production issues. The biggest benefit was not just the time saving but being able to identify the root cause with much greater confidence instead of manually correlating logs from multiple services.
We did not calculate a formal ROI specifically for Honeycomb Enterprise, so I cannot give an exact financial figure. The biggest return has been in time saving and operational efficiency. Based on my experience, our troubleshooting time for complex production incidents improved by roughly 40 to 50 percent, with issues that previously took hours to isolate often being narrowed down to 20 to 30 minutes. This helps the organization reduce disruption and improve our mean time to resolution. We have not reduced headcount because of Honeycomb Enterprise. Instead, it allows our engineering team to spend less time firefighting and more time delivering new features and platform improvements. From that perspective, the productivity gains have provided a strong return on investment.
Which other solutions did I evaluate?
We looked at a few other observability platforms before settling on Honeycomb Enterprise, and the main ones were DataDog, Dynatrace, New Relic, Grafana, and Prometheus for metrics. Each of them had strengths, but Honeycomb Enterprise stood out for distributed tracing and high cardinality data, as well as the ability to perform ad hoc investigations without having to predefine dashboards or indexes. Since we run a Kubernetes-based microservice environment, that flexibility made troubleshooting much faster. We also appreciated its strong OpenTelemetry support, which fits well with our observability strategy. Ultimately, Honeycomb Enterprise gave us the best balance of deep troubleshooting capability and ease of investigating complex production issues.
What other advice do I have?
I would say that Honeycomb Enterprise takes governance and security very seriously. I appreciate that it supports enterprise features such as role-based access control, SSO integration, and audit capabilities, which are important for controlling access to observability data. From an AI perspective, I see the AI features more as an assistant for integration rather than something making autonomous decisions, which is the right approach for production environments. I still want engineers to validate recommendations before taking actions. Overall, I would say the governance and security are strong, and I would always prefer to see continuous improvement around access control areas, data privacy options, and transparency into how AI generates insights and processes data, especially for organizations with very strict compliance requirements.
The AI capabilities are generally accurate and reliable, especially when used to assist with integration rather than replacing engineering judgment. The suggestions and insights usually surface patterns that I might not notice immediately. That being said, I do not treat AI output as my final answer. I always validate it against distributed traces, telemetry, and application logs before making production decisions. Overall, I rate the AI accuracy high for accelerating root cause analysis, but I still see it as a decision support tool rather than an autonomous troubleshooting solution.
My advice would be to invest time in planning an observability strategy before rolling it out and instrument your applications. I would also recommend instrumenting your applications with OpenTelemetry from the beginning and focusing on collecting meaningful telemetry instead of trying to capture everything. Start with your most critical service and build from there. I also recommend training the engineering team on distributed tracing and Honeycomb Enterprise query capability because that is where you will get the most value. Finally, monitor your telemetry volume and retention policy to keep costs under control as your environment grows. If you approach it that way, Honeycomb Enterprise becomes a very powerful tool for troubleshooting, performance optimization, and improving the reliability of your cloud-native applications. I rate this product a 9 out of 10 overall.