Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Reporter does not always report data #23

Open
MikeMcMahon opened this issue Nov 5, 2020 · 1 comment
Open

Reporter does not always report data #23

MikeMcMahon opened this issue Nov 5, 2020 · 1 comment

Comments

@MikeMcMahon
Copy link

I'm developing an application with Go 1.12

I set the ProxyConfiguraiton() to flush every 60s and Reporter to report every 60s. With this configuration, we observed periods where the data is reported sporadically, maybe 3-5m of data sent, and then a period of time where it is 2-3 minutes of no data sent at all.

2020/11/05 14:38:58 resetting wavefront proxy connection
2020/11/05 14:38:58 write tcp 10.101.3.2:59327->10.100.191.182:2878: i/o timeout
2020/11/05 14:38:58 connected to Wavefront proxy at address: wf-proxy.mgmt.internal.lacework.net:2878

The above messages occur about every minute or so.

My first thought was we had some issue with the data being flushed at the same frequency we are sending (strange but I wanted to see) so I tightened up the Sender interval to every second, so that it would flush data every second. This however made the problem worse. My log is now filled with broken pipe exceptions after about 1-2 minutes of sending data and I never am able to send data again.

I am currently trying to play with values to see what works and does not work so that data will properly report; however, something is not working properly in the library and may be related to changes in Go 1.12 golang/go#35373.

@MikeMcMahon
Copy link
Author

30 flush interval and 60s report interval seems to be mostly immune from this failure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant