Currently the external stats senders for Graphite and OpenTSDB/KairosDB just attempt to slam their buffers into a socket, and if the local OS doesn't have an issue with that, it considers the request sent. For these simple protocols there isn't very much more we can do, as no ack is returned. However, people implementing their own outbound protocols may benefit from having a little more complexity available to them in the stats sender, especially once stats sender can be configured to be persistent. Right now the trade-offs involved favor simply registering as a listener manually and rolling your own sender if more resilience is required.
Currently the external stats senders for Graphite and OpenTSDB/KairosDB just attempt to slam their buffers into a socket, and if the local OS doesn't have an issue with that, it considers the request sent. For these simple protocols there isn't very much more we can do, as no ack is returned. However, people implementing their own outbound protocols may benefit from having a little more complexity available to them in the stats sender, especially once stats sender can be configured to be persistent. Right now the trade-offs involved favor simply registering as a listener manually and rolling your own sender if more resilience is required.