Honeycomb VS NeuVector

I haven't used anything else, but I'll gladly shill for https://honeycomb.io. - Source: Hacker News / 7 months ago

With all of this in place I went a step further and added Opentelemetry to track the stats of how often the routine was being triggered on Honeycomb. - Source: dev.to / 11 months ago

Events can be used in many meaningful ways. The Event subsystem of B is pretty much a co-evolution of what honeycomb.io offers, but implemented completely differently - it is on bare-metal, and hence a lot cheaper. Because of that, B never subsampled, but always kept a full low of all events anywhere, no exceptions. Source: 12 months ago

It should be noted that this is a very oblique ad for http://honeycomb.io. That in no way impugns the content of the post, and in fact, it's given the content of the post that I feel compelled to point out that, ultimately, this is an ad. Because what is sales and advertising, anyway? It's just a way to get you to buy a product, and you can't do that if you've never even heard about the product. I'm not currently... - Source: Hacker News / about 1 year ago

Very cool to see honeycomb.io is doing that. I'm about to embark on my distributed tracing learning journey, this makes me want to try honeycomb right away. Source: about 1 year ago

For Containers -> https://neuvector.com/ its the best on the market for DPI. Source: about 1 year ago

You should check out NeuVector for any public exposed Kubernetes/EKS. Runs inside the cluster, no SaaS, inspects network traffic at layer 7, deploys via helm, no sidecars, no agents, no eBPF kernel shim bs, no muss, no fuss. Also scans for vuls/security checks (CIS) and has expanded PSP policies integrated into EKS admission controller. Source: almost 2 years ago