Change default flushInterval
See original GitHub issueThe flushInterval
config option defaults to 60 seconds today. That’s too long and is a left over from the Opbeat agent where all requests from all Opbeat users was sent to one single endpoint. A better default would probably be something like 30 seconds.
When changing the default, remember to update the documentation as well.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
flushInterval - IBM
Syntax. flushInterval = interval ... This entry is used when the useDiskCache entry is set to auto or never . Default value. The...
Read more >Default values of Kafka log.flush.interval.messages and log ...
I wonder what values of log.flush.interval.messages and log.flush.interval.ms are when I leave them commented in Kafka server config file? Are there any default...
Read more >Mobile: Customize Flush Interval - Mixpanel Help Center
Events and User data sent to Mixpanel gets queued and flushed at certain intervals by default. This interval can be adjusted to flush...
Read more >Decrease flushInterval or make it configurable #18 - GitHub
I'd be great to either decrease the default or make it configurable with a flag. Anything else you would like to add: [Miscellaneous...
Read more >Introduction to StatsD | HostedMetrics
The default flush interval in StatsD is 10 seconds, which means that every ten seconds, ... the flushInterval in StatsD is set to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I didn’t make the change yet, but I was suggesting 10s when we discussed it a couple of weeks ago.
This was solved in #186