The solution is mainly used for stack observability. It observes service behavior or any kind of failure that may be happening. The tool is also related to research. My company is working more on this, but I have been working on my SLOs and defining SLOs for the last seven months.
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
2 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Easy to use and the dashboard is very intuitive
What is our primary use case?
What is most valuable?
The solution's most valuable features are the queries for the OpenTelemetry events and all the tracing. The solution is very easy to use, and the dashboard is very intuitive.
What needs improvement?
We faced some OpenTelemetry metrics lost between the communication from the service and the Honeycomb.io. I can't say if this is a Honeycomb.io issue or if there are some limitations in OpenTelemetry.
Alerts are very helpful in Honeycomb.io, but we don't usually merge because we can compare queries with queries for making alerts. We can make alerts based on static numbers, which may block us from building alerts that could be generic enough or could be serviced.
For how long have I used the solution?
I have been using Honeycomb.io for two years.
What do I think about the stability of the solution?
We’ve never had any issues with the solution’s stability.
What do I think about the scalability of the solution?
Honeycomb.io is a scalable solution. The service is very resilient and can handle a lot of data. The quantity of data Honeycomb.io can parse and use to create charts is really good. More than 100 users are using the solution in our tech team.
I rate the solution’s scalability an eight or nine out of ten.
How was the initial setup?
The solution's initial setup is easy. I think the hardest part is to understand OpenTelemetry in general.
What other advice do I have?
We set up Honeycomb.io on all the services so that we can have all the set traces of the communication between all the services inside the company. This helps us understand where it could be failing, which in turn helps with failures and observability.
When we are not thinking about one specific failure but a major one, we can create queries for statistics views like the P99 or P95 behaviors. That's very helpful. I would recommend the solution to other users because it is very helpful.
Overall, I rate the solution a nine out of ten.
Honeycomb is a great and much cheaper alternative to Datadog
What do you like best about the product?
- It's cheaper than Datadog
- Distributed tracing works fairly well
- The SDKs follow open telemetry conventions
- Distributed tracing works fairly well
- The SDKs follow open telemetry conventions
What do you dislike about the product?
- Support is pretty slow to respond
- The SDKs could be better
- Documentation is undiscoverable
- The SDKs could be better
- Documentation is undiscoverable
What problems is the product solving and how is that benefiting you?
- Distributed tracing
- Measuring database query performance
- Measuring database query performance
showing 1 - 2