Airbrakes lack of processing where different errors would be perceived as the same occurrence, lack of stacktraces and other minor annoyances.
It's definitely a great idea for a service but the current state of Erlang integration does not give me anything useful compared to our current solution (custom error handler which feeds Riemann and graphite).
Example error:
[tcp] Prod CRASH REPORT Process <0.1589.0> with 0 neighbours exited with reason: no case clause matching {state,#Port<0.2740>,ranch_tcp,undefined,5000,9,{lqrc_backend,undefined},<<0,2,14,255,252,0,0,0,0,150,111,220,1,93,1,93,2,0,1,0,35,2,0,0,0,52,5,0,0,181,3,3,41,221,2,123,2,14,1,168,14,1,94,136,160,104,220,0,8,7,86,2,0,1,0,35,2,0,0,0,105,5,0,0,155,2,2,46,141,1,155,2,14,2,46,9,232,100,228,154,104,220,5,48,7,113,2,0,1,0,35,2,0,0,0,110,5,0,0,131,2,2,164,230,0,1,2,14,1,176,10,25,100,4,154,102,220,0,1,7,203,2,0,1,0,35,2,0,0,0,12,5,0,0,136,2,2,67,20,0,79,2,14,1,250,10,194,98,48,158,104,220,0,7,7,255,...>>,...} in tm_protocol:handle_info/2 line 83 in gen_server:terminate/6 line 744
-- User feedback . Stored here for future work --
Airbrakes lack of processing where different errors would be perceived as the same occurrence, lack of stacktraces and other minor annoyances.
It's definitely a great idea for a service but the current state of Erlang integration does not give me anything useful compared to our current solution (custom error handler which feeds Riemann and graphite).
Example error:
[tcp] Prod CRASH REPORT Process <0.1589.0> with 0 neighbours exited with reason: no case clause matching {state,#Port<0.2740>,ranch_tcp,undefined,5000,9,{lqrc_backend,undefined},<<0,2,14,255,252,0,0,0,0,150,111,220,1,93,1,93,2,0,1,0,35,2,0,0,0,52,5,0,0,181,3,3,41,221,2,123,2,14,1,168,14,1,94,136,160,104,220,0,8,7,86,2,0,1,0,35,2,0,0,0,105,5,0,0,155,2,2,46,141,1,155,2,14,2,46,9,232,100,228,154,104,220,5,48,7,113,2,0,1,0,35,2,0,0,0,110,5,0,0,131,2,2,164,230,0,1,2,14,1,176,10,25,100,4,154,102,220,0,1,7,203,2,0,1,0,35,2,0,0,0,12,5,0,0,136,2,2,67,20,0,79,2,14,1,250,10,194,98,48,158,104,220,0,7,7,255,...>>,...} in tm_protocol:handle_info/2 line 83 in gen_server:terminate/6 line 744