Hello Neil, On Tue, Apr 30, 2013 at 01:50:30PM -0700, Neil Mckee wrote: > Hello All, > > I had a go at adding standard sFlow instrumentation to haproxy: > https://github.com/sflow/haproxy > > This implements the exact same binary-logging-over-UDP export that you get > from mod-sflow for apache, nginx-sflow-module, tomcat-sflow-valve, and more. > It supports random 1-in-N sampling for scalability, and it is designed to be > integrated with host performance counters from hsflowd, along with sFlow > traffic monitoring from most network switches. (The goal being holistic > end-to-end visibility). > > Anyone want to try it out? (...)
First, thank you for this work. I'm realizing that it can be frustrating to see no response to your post, but we probably need more time to get some testers. Let me knwo if you want me to add a link from the main page to you work. I must say I have zero experience with sflow, so please don't take my ignorance as a criticism of your work ! While I understand why it can be useful at the network level, it's still hard for me to understand the benefit at upper layers, since more precise details can be deduced from the logs probably at a lower cost since the work just has to be done once. Maybe you could enlighten me on this (and probably others as well, as it's likely that I'm not the only one who doesn't see an obvious benefit from doing this). Best regards, Willy
