An easy replacement for original node's version is not working #8

Closed
fluential opened this Issue Nov 20, 2012 · 1 comment

Projects

None yet

2 participants

@fluential

I think this version doesn't submit properly to graphite's carbon instance, I can see 'None' values, when switched to nodejs version I immediately get stats back.

My nodejs config looks like that:
{
graphitePort: 2003
, graphiteHost: "127.0.0.1"
, port: 8125
}

So the way i test it:
./statsd -p 8127 -m 8128 -d -R 127.0.0.1 -d
I bind to another port

and i am using the following script:

---- test.sh ---

!/bin/bash

nc -w 1 -u 127.0.0.1 8127 << EOF
statsd.test:$RANDOM|c
EOF

which I run like that:
while :;do bash test.sh ;sleep 1;done

After receiving few packets which I can see via debug mode I can see:

statsd-c[3820]: Found key name 'statsd_test'
statsd-c[3820]: Found value '21670.000000'
statsd-c[3820]: i = 3
statsd-c[3820]: After loop, i = 2, value = 21670.000000
statsd-c[3820]: freeing key and value
statsd-c[3820]: update_stat ( messages, last_msg_seen, 1353413734 )
statsd-c[3820]: HASH_FIND 'messages' 'last_msg_seen'
statsd-c[3820]: Updating old stat entry
statsd-c[3820]: Stats dump:
statsd-c[3820]: graphite.last_flush: 1353413634
statsd-c[3820]: messages.last_msg_seen: 1353413734
statsd-c[3820]: messages.bad_lines_seen: 0
statsd-c[3820]: Counters dump:
statsd-c[3820]: statsd_test: 175201.000000
statsd-c[3820]: Gauges dump:
Messages:
stats.statsd_test 17520.100000 1353413743
stats_counts_statsd_test 175201.000000 1353413743
statsd.numStats 1 1353413743
statsd-c[3820]: Stats dump:
statsd-c[3820]: graphite.last_flush: 1353413634
statsd-c[3820]: messages.last_msg_seen: 1353413734
statsd-c[3820]: messages.bad_lines_seen: 0
statsd-c[3820]: Counters dump:
statsd-c[3820]: statsd_test: 0.000000
statsd-c[3820]: Gauges dump:

But I don't see anything showing up in graphite...

@jbuchbinder jbuchbinder was assigned Nov 20, 2012
Owner

Graphite submission code was stubbed. Patched in test graphite submission code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment