@@ -336,9 +336,9 @@ ENABLE_TAGS = True
336336# from the [cache] section.
337337# You can then specify the --instance=b option to manage this instance
338338#
339- # In order to turn off logging of successful connections for the line
340- # receiver, set this to False
341- # LOG_LISTENER_CONN_SUCCESS = True
339+ # In order to turn on logging of successful connections for the line
340+ # receiver, set this to True
341+ LOG_LISTENER_CONN_SUCCESS = False
342342
343343[relay]
344344LINE_RECEIVER_INTERFACE = 0.0.0.0
@@ -488,9 +488,9 @@ USE_FLOW_CONTROL = True
488488# CARBON_METRIC_PREFIX = carbon
489489CARBON_METRIC_INTERVAL = 10
490490#
491- # In order to turn off logging of successful connections for the line
492- # receiver, set this to False
493- # LOG_LISTENER_CONN_SUCCESS = True
491+ # In order to turn on logging of successful connections for the line
492+ # receiver, set this to True
493+ LOG_LISTENER_CONN_SUCCESS = False
494494
495495# If you're connecting from the relay to a destination that's over the
496496# internet or similarly iffy connection, a backlog can develop because
@@ -625,8 +625,8 @@ MAX_AGGREGATION_INTERVALS = 5
625625CARBON_METRIC_INTERVAL = 10
626626
627627# In order to turn off logging of successful connections for the line
628- # receiver, set this to False
629- # LOG_LISTENER_CONN_SUCCESS = True
628+ # receiver, set this to True
629+ LOG_LISTENER_CONN_SUCCESS = False
630630
631631# In order to turn off logging of metrics with no corresponding
632632# aggregation rules receiver, set this to False
0 commit comments