github/evenflow

sFlow to Graphite bridge

evenflow's Issues

evenflow.rb:117: undefined method `[]' for nil:NilClass (NoMethodError)

I could not get this to run. As soon as I get some metrics, in this case from a Vyatta firewall, it tanks with the following errors...

root@host01:# CARBON_PREFIX=network CARBON_URL=carbon://10.x.x.x:2003 STATS_INTERVAL=300 ruby evenflow.rb
evenflow.rb:117: undefined method []' for nil:NilClass (NoMethodError) from evenflow.rb:114:ineach'
from evenflow.rb:114
from evenflow.rb:112:in each' from evenflow.rb:112 from evenflow.rb:111:ineach'
from evenflow.rb:111
from /var/lib/gems/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:951:in call' from /var/lib/gems/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:951:inrun_deferred_callbacks'
from /var/lib/gems/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:187:in run_machine' from /var/lib/gems/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:187:inrun'
from evenflow.rb:12

My test host in case sending metrics was a Vyatta firewall. I'm running evenflow on a Ubuntu 12.04 host with stock ruby pkgs, a gem install of most deps before attempting/doing a bundle install of evenflow. Hopefully you can shed some light on the above.

Other -- we know our Vyatta sends appropriate sflow data as pmacctd instance set up as an sflow receiver can see it fine where as sflow2graphite or evenflow just bomb getting sflow from the Vyatta. We know the Vyatta sflow component is pmacct based, so fairly standard in terms of data being sent.

Thanks for your assistance.

Evenflow blows up on DNS failure.

If the source IP that is sending metrics to evenflow isn't in DNS, the process crashes. We should just ignore metrics from hosts that are not in DNS and emit a log line instead.

/usr/lib/ruby/1.8/resolv.rb:398:in `getname': DNS result has no information for 172.16.18.254 (Resolv::ResolvError)
        from ./evenflow.rb:66
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1037:in `call'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1037:in `spawn_threadpool'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1033:in `initialize'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1033:in `new'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1033:in `spawn_threadpool'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:1023:in `defer'
        from ./evenflow.rb:83
        from /data/evenflow/vendor/gems/ruby/1.8/gems/em-sflow-1.0.1/lib/em-sflow/datagram_handler.rb:25:in `call'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/em-sflow-1.0.1/lib/em-sflow/datagram_handler.rb:25:in `receive_data'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/em-sflow-1.0.1/lib/em-sflow/datagram_handler.rb:24:in `each'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/em-sflow-1.0.1/lib/em-sflow/datagram_handler.rb:24:in `receive_data'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:187:in `run_machine'
        from /data/evenflow/vendor/gems/ruby/1.8/gems/eventmachine-1.0.0/lib/eventmachine.rb:187:in `run'
        from ./evenflow.rb:10