I am experiencing errors on production system under high load (which means statsderl is called very frequently). Those errors are crashing statsderl application, which in turn causes to whole erlang interpreter termination.

I get in logs:

16:43:50.808 [error] CRASH REPORT Process statsderl_1 with 0 neighbours crashed with reason: no function clause matching statsderl_server:handle_msg({inet_reply,#Port<0.170403>,{error,eperm}}, {state,<<31,189,149,202,194,181,112,114,111,100,117,99,116,105,111,110,46,100,100,98,45,109,101,...>>,...}) line 46
16:43:50.808 [error] Supervisor statsderl_sup had child undefined started with statsderl_server:start_link(statsderl_1) at <0.4125.5> exit with reason function_clause in context child_terminated
16:43:50.991 [error] CRASH REPORT Process statsderl_1 with 0 neighbours crashed with reason: no function clause matching statsderl_server:handle_msg({inet_reply,#Port<0.177218>,{error,eperm}}, {state,<<31,189,149,202,194,181,112,114,111,100,117,99,116,105,111,110,46,100,100,98,45,109,101,...>>,...}) line 46
16:43:50.992 [error] Supervisor statsderl_sup had child undefined started with statsderl_server:start_link(statsderl_1) at <0.10894.5> exit with reason function_clause in context child_terminated
16:43:50.992 [error] Supervisor statsderl_sup had child undefined started with statsderl_server:start_link(statsderl_1) at <0.10894.5> exit with reason reached_max_restart_intensity in context shutdown
16:43:50.992 [info] Application statsderl exited with reason: shutdown
16:43:50.992 [error] gen_server <0.193.0> terminated with reason: unexpected_delivery_and_no_default_consumer
16:43:50.993 [error] gen_server <0.207.0> terminated with reason: unexpected_delivery_and_no_default_consumer
16:43:50.993 [error] CRASH REPORT Process <0.207.0> with 0 neighbours exited with reason: unexpected_delivery_and_no_default_consumer in gen_server2:terminate/3 line 1145
16:43:50.993 [error] CRASH REPORT Process <0.193.0> with 0 neighbours exited with reason: unexpected_delivery_and_no_default_consumer in gen_server2:terminate/3 line 1145
{"Kernel pid terminated",application_controller,"{application_terminated,statsderl,shutdown}"}

It happens only when system is under high load. Under smaller load everything works just fine. Als changing rate parameter in statsderl calls does not seem to make any difference.

I am running most resent statsderl v0.4.3.

i miss my uncle

I don't know why.
But when I remove statsderl, it gets fine.

Erlang/OTP 20 was released today, however it seems like statsderl breaks with this new release.

Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V9.0  (abort with ^G)
1> statsderl_app:start().
{ok,[granderl,statsderl]}
2> statsderl:counter("a", 1, 1).
ok
3>
=ERROR REPORT==== 21-Jun-2017::16:24:52 ===
[statsderl] inet_reply error: eafnosupport

TODO:

• Add new environment var called hosts
• Modify server code to accept hostname/port arguments

from #10

For cases where no Environments variables are set, or usage of other config tools like confetti. Would be nice to have possibility to start the application passing parameters, instead of having them being read hardcoded in ENV vars.

If this turns to be a case, I'd be glad to add the possibility without breaking backward compatibility

Hey! Would you be okay to create a tag for version 0.3.6?

from #12

I find it useful to be able to mix tokens within base_key. With my proposed change one can have composite base key, for example:

{base_key, ["development", hostname, "my-app"]}

#48

Hi

How to set the statsd server address.
How do i modify the defaults

-define(DEFAULT_BASEKEY, undefined).
-define(DEFAULT_HOSTNAME, {127, 0, 0, 1}).

I see that it could be set using

{env, [{Key, Val}]} in statsderl.app.

But I wish to add the statsderl as a dependency to rebar or erlang.mk. Not to modify the existing dependency.

Please advise. Did I understand any thing wrong

The function statsderl_pool:send/2 returns either the atom ok or the value of Msg. However, all functions that call send directly or indirectly (e.g., through cast and operation) are declared as returning only the atom ok, for example statsderl_pool:sample/2.

I recommend that we modify the body of send/2 to send the message to the server and then explicitly return the atom ok.

In using the module, I discovered that timing_fun's spec is expecting the function result that is being timed to always be ok. Due to this, dialyzer will fail for timing any functions that have a non-ok return

Few things:

1. I want to start it as a background process, rather than from erl.
2. Right now it is sending stats (when used along with vmstats) on UDP ports on localhost (lo interface), I want the messages on eth0 and on the ip.
3. How should I send my messages(datapoints) to graphite.

I am new to the erlang world, sorry if I ask something stupid.

According to the StatsD spec (the only one available...) histograms and meters are part of the protocol, but statsderl currently does not support these metrics:

https://github.com/b/statsd_spec
https://github.com/etsy/statsd/wiki/Protocol

Other clients that do support these metrics:

Codahale StatsD reporter: https://github.com/organicveggie/metrics-statsd/blob/master/src/main/java/com/bealetech/metrics/reporting/StatsdReporter.java#L129
Go: https://github.com/alexcesaro/statsd/blob/master/statsd.go