make the memory leak bug clearer

see #50

README.md

@@ -31,6 +31,8 @@ Limitations
 
 * regex rewriter rules do not support limiting number of replacements, max must be set to -1
 * the web UI is not always reliable to make changes.  the config file and tcp interface are safer and more complete anyway.
+* internal metrics *must* be routed somewhere (e.g. into the relay itself) otherwise it'll [leak memory](https://github.com/graphite-ng/carbon-relay-ng/issues/50).
+  this is a silly bug but I haven't had time yet to fix it.
 
 
 Releases & versions

examples/carbon-relay-ng-docker.ini

@@ -33,6 +33,9 @@ init = [
 ]
 
 [instrumentation]
-# in addition to serving internal metrics via expvar, you can optionally send em to graphite
-graphite_addr = "localhost:2003" #  feed back into the relay itself
+# in addition to serving internal metrics via expvar, you can send them to graphite/carbon
+# IMPORTANT: setting this to "" will disable flushing, and metrics will pile up and lead to OOM
+# see https://github.com/graphite-ng/carbon-relay-ng/issues/50
+# so for now you MUST send them somewhere. sorry.
+graphite_addr = "localhost:2003"
 graphite_interval = 1000  # in ms

examples/carbon-relay-ng.ini

@@ -53,6 +53,9 @@ amqp_vhost = "/graphite"
 amqp_exchange = "metrics"
 
 [instrumentation]
-# in addition to serving internal metrics via expvar, you can optionally send em to graphite
-graphite_addr = ""  # localhost:2003 (how about feeding back into the relay itself? :)
+# in addition to serving internal metrics via expvar, you can send them to graphite/carbon
+# IMPORTANT: setting this to "" will disable flushing, and metrics will pile up and lead to OOM
+# see https://github.com/graphite-ng/carbon-relay-ng/issues/50
+# so for now you MUST send them somewhere. sorry.
+graphite_addr = "localhost:2003"
 graphite_interval = 1000  # in ms