Listing Thumbnail

    Honeycomb Enterprise

     Info
    Deployed on AWS
    Honeycomb helps DevOps, SRE, and engineering teams understand and troubleshoot complex relationships within distributed services. See how services are performing, and drill down to issues with individual users without having to correlate and make guesses across different data types.
    3.9

    Overview

    Honeycomb is an observability platform for cloud native apps that gives you high-level data regarding how your services are performing, combined with the ability to drill down all the way to the individual user level to troubleshoot issues without having to hop across different data types to piece the data together.

    Traditionally, when debugging production incidents with dashboards and metrics, it is difficult to drill down beyond aggregate measures. For example, a graph with error rates can't tell you which exact customers are experiencing the most errors. Logs can show you the raw error data, but it's hard to see the bigger patterns unless you know exactly where to look.

    Honeycomb's event-based telemetry model and its powerful query engine make it possible to slice your data across billions of rows and thousands of fields to find hidden patterns. The ability to quickly get results means teams can resolve incidents faster and figure out where to make system optimizations.

    Teams using Honeycomb ship faster, have faster MTTR, happier customers and less alert fatigue and burnout.

    For custom pricing, EULA, or a private contract, please contact AWS-Marketplace@honeycomb.io  for a private offer.

    Highlights

    • Faster Incident Response. Quickly locate sources of problems across complex applications. Use distributed tracing to find issues buried deeply within your stack.
    • Treat Performance Like a Feature. Slow is the new down. Honeycomb is designed to help teams make smart investments in optimizing performance for better user experiences.
    • Release Features Faster. Unknown unknowns in production make teams fear deploying. Honeycomb helps you understand production in ways that others simply chalk up as unknowable. With Honeycomb you ship more features faster, with fewer failures.

    Details

    Delivery method

    Deployed on AWS

    Features and programs

    Buyer guide

    Gain valuable insights from real users who purchased this product, powered by PeerSpot.
    Buyer guide

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Honeycomb Enterprise

     Info
    Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    12-month contract (1)

     Info
    Dimension
    Description
    Cost/12 months
    Honeycomb
    Honeycomb AWS Marketplace Public Listing
    $50,000.00

    AI Insights

     Info

    Dimensions summary

    This listing bills through a single contract dimension, measured in Honeycomb units. Rather than fixed tiers, you agree to a custom contract that fits your usage. Pricing scales with the volume of telemetry events you send to the platform. Your event volume drives the allowance you purchase. You can add more capacity to your contract as your applications grow. This structure keeps costs tied to how much data you ingest, not to seats or querying, which are not billed separately here.

    Top-of-mind questions for buyers

    An event is a single record of telemetry you send, such as one span in a trace or one structured log line. You can attach unlimited custom fields to each event without changing its count. Metrics data points are tracked separately from events.
    Enterprise plans start with a base allowance of billions of events per year. If your applications send more, you can add capacity to your contract whenever you need it. Cost scales with the volume of events you ingest, so more telemetry means a higher allowance.
    No. This contract bills on event volume alone. You get unlimited seats and unlimited querying without extra charges. Custom metrics and high-cardinality fields do not add fees. Only the amount of telemetry data you send drives what you pay.
    www.honeycomb.io+1
    Helpful?

    Vendor refund policy

    Please contact sales.

    Custom pricing options

    Request a private offer to receive a custom quote.

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Software as a Service (SaaS)

    SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.

    Resources

    Vendor resources

    Support

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Comparison

     Info
    Updated weekly

    Accolades

     Info
    Top
    10
    In Log Analysis
    Top
    10
    In Application Performance and UX Monitoring
    Top
    10
    In Observability, Monitoring and Observability

    Customer reviews

     Info
    Sentiment is AI generated from actual customer reviews on AWS and G2
    Reviews
    Functionality
    Ease of use
    Customer service
    Cost effectiveness
    8 reviews
    Insufficient data
    Positive reviews
    Mixed reviews
    Negative reviews

    Overview

     Info
    AI generated from product descriptions
    Event-Based Telemetry Model
    Utilizes event-based telemetry architecture to capture and analyze detailed observability data across distributed systems.
    Distributed Tracing Capability
    Implements distributed tracing functionality to identify and locate issues buried deeply within application stacks across complex services.
    Advanced Query Engine
    Provides a powerful query engine capable of slicing data across billions of rows and thousands of fields to identify hidden patterns and anomalies.
    Multi-Level Data Drill-Down
    Enables drilling down from high-level service performance metrics to individual user-level issues without requiring correlation across different data types.
    Cloud Native Application Observability
    Designed for observability of cloud native applications with integrated support for monitoring service performance and troubleshooting distributed services.
    Data Ingestion and Query Performance
    Ingests petabytes of telemetry per day with capability to process hundreds of terabytes and execute tens of millions of queries daily without performance degradation
    Knowledge Graph Architecture
    Utilizes O11y Knowledge Graph to structure and correlate data across logs, metrics, and traces for fast search and correlation capabilities
    Natural Language Processing for Incident Analysis
    Implements O11y AI to enable troubleshooting of complex incidents using natural language queries for accelerated root cause analysis
    Open Data Lake Foundation
    Built on Snowflake data lake architecture providing open data storage without vendor lock-in and enabling cost-efficient telemetry retention
    Multi-Signal Correlation
    Correlates and contextualizes data across logs, metrics, and traces to provide unified observability across multiple teams and use cases
    Request Tracing Granularity
    Captures 100% of all requests in real-time with 1-second granularity, ensuring complete visibility without sampling
    Automated Root Cause Analysis
    Built-in automation and AI-driven root cause analysis with recommendations for faster issue resolution
    Full-Stack Visibility
    Provides full-stack visibility across application code, Kubernetes containers (EKS/ECS), and micro-services with dependency mapping
    Technology Integration Support
    Supports over 300 technology integrations including AWS services, cloud platforms, micro-services, and containerized environments
    Intelligent Alerting System
    SmartAlerts feature delivers tailored alerts based on application performance monitoring across the full stack

    Contract

     Info
    Standard contract
    No

    Customer reviews

    Ratings and reviews

     Info
    3.9
    22 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    41%
    45%
    14%
    0%
    0%
    15 AWS reviews
    |
    7 external reviews
    External reviews are from G2  and PeerSpot .
    reviewer2894310

    Observability platform has transformed how I trace backend latency and pinpoint API bottlenecks

    Reviewed on Nov 20, 2026
    Review from a verified AWS customer

    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?

    public cloud deployment, mainly as a SaaS platform

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Abdul Samad Irfan Shaik

    Observability has transformed microservice troubleshooting and now reduces payment flow outages

    Reviewed on Nov 19, 2026
    Review from a verified AWS customer

    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?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Manoday Ahire

    Observability has transformed how my team pinpoints bottlenecks and resolves production issues

    Reviewed on Nov 09, 2026
    Review from a verified AWS customer

    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?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Yash Dhameliya

    Observability has improved debugging speed and now helps trace complex user-specific issues

    Reviewed on Oct 27, 2026
    Review from a verified AWS customer

    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.

    AkshayChaudhari

    Observability has improved troubleshooting speed but still needs a gentler learning curve

    Reviewed on Oct 22, 2026
    Review provided by PeerSpot

    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.

    View all reviews