carbon-relay-ng

• build packages for ubuntu, debian, centos and automatically push to circleCI upon successfull builds (https://github.com/graphite-ng/carbon-relay-ng#installation)
• add pickle input (#140)
• publish dashboard on grafana.net
• fix build for go <1.6 (#118)
• allow overriding docker commandline (#124)
• validation: tuneable validation of metrics2.0 messages. switch default legacy validation to medium, strict was too strict for many. show validation level in UI. Add time-order validation on a per-key basis
• support rewriting of metrics
• document limitations
• grafana.net route updates and doc updates
• re-organize code into modules
• various small improvements
• remove seamless restart stuff. not sure anymore if it still worked, especially now that we have two listeners. we didn't maintain it well, and no-one seems to care

known issues:
there's some open tickets on github for various smaller issues, but one thing that has been impacting people a lot for a long time now is memory usage growing indefinitely when instrumentation is not configured (because it keeps accumulating internal metrics).
The solution is to configure graphite_addr to an address it can send metrics to (e.g. its own input address)
see ticket 50 for more info

changes:

• regex / substring / prefix support for blacklist
• support more management functionality in admin UI + show dest online status
• properly set default endpoint settings
• configurable maxprocs setting
• consistent hashing (functions same as in official carbon but without replication >1)
• pidfile support
• include example init file & dockerfile
• switch to govendor for native vendoring && update some dependencies
• UDP listener
• pull in js libraries over https
• make validation configurable
• update included dashboard for grafana3
• rate controls for profiling
• experimental new grafana.net hosted metrics route
• refactored imperatives (commands) parsing
• fix versioning when building packages

• lots of code refactoring. non-blocking operations
• new config format with imperative commands
• extensive internal stats & grafana dashboard
• a more extensive routing system (which can support round robin & hashing) (see #23)
• aggregators
• use party tool for vendoring dependencies
• metric validator with json endpoint for inspection
• performance fixes

probably more. (was blacklists new?)
note: the admin interfaces need more work.

initial, simple version that used commandline args to configure. no admin interfaces
basically the version written by Richard Crowley with some minor patches

note that this version uses blocking sends (1 endpoint down blocks the program)

extended version with config file, http and telnet interfaces, statsd for internal instrumentation, disk spooling support, but still blocking sends