xandkar beam_stats issues

xandkar / beam_stats

Collect detailed Erlang VM metrics and send to arbitrary, pluggable backends (StatsD and Graphite backends included).

MIT License

17 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Add a process-provenance-graph consumer

#28 xandkar opened 2 years ago
0
Compile with OTP 24 and made it work with statser

#27 mcesaro closed 2 years ago
1
Fix log msg format

#26 xandkar closed 8 years ago
0
Bad format in log messages

#25 xandkar closed 8 years ago
1
And enable/disable per-ets-table stats config

#24 xandkar opened 9 years ago
0
Support chunking in Graphite backend

#23 xandkar opened 9 years ago
0
Collect ports stats

#22 xandkar opened 9 years ago
0
Use iolists, where appropriate

#21 puzza007 closed 9 years ago
1
Collect per process reductions deltas

#20 xandkar closed 9 years ago
0
Deltas server

#19 xandkar closed 9 years ago
0
Implement generic deltas server

#18 xandkar closed 9 years ago
1
Collect number of processes per origin

#17 xandkar opened 9 years ago
0
Collect number of ETS tables per name

#16 xandkar opened 9 years ago
0
Collect reductions deltas per process

#15 xandkar closed 9 years ago
1
Aggregate ETS table data: rollup all tables with the same name

#14 xandkar closed 9 years ago
1
Aggregate anonymous process data by process origin

#13 xandkar closed 9 years ago
0
Factor and abstract graphite msg

#12 xandkar closed 9 years ago
0
Aggregate anonymous process data in StatsD and Graphite consumers

#11 xandkar closed 9 years ago
1
Handle undefined value from erlang:process_info/2

#10 xandkar closed 9 years ago
1
Test full produce consume cycle

#9 xandkar closed 9 years ago
0
Factor-out the idea of periodic (produce -> package -> transport) as freight line library

#8 xandkar opened 9 years ago
0
Abstract graphite message and graphite to statsd message transformations

#7 xandkar closed 9 years ago
1
Test the full produce/consume cycle, not just consume

#6 xandkar closed 9 years ago
1
Allow custom, static node name in StatsD consumer.

#5 xandkar closed 9 years ago
0
Consider accumulating StatsD messages in the process mailbox, rather than concatenating lists

#4 xandkar opened 9 years ago
1
Add process stats

#3 xandkar closed 9 years ago
0
Per ets table stats

#2 xandkar closed 9 years ago
0
Use module() instead of atom() where applicable

#1 puzza007 closed 9 years ago
1