Forced Due to Logging Gap what does this mean

Question

It seems to be new in SP 2013 that when monitoring the ULS logs there are large instances of the phrase
Forced due to logging gap :
Can someone advise as to the exact meaning of this? There are extremely few references on the net, only a few examples of people posting their ULS entries for unrelated questions.
Seems a bit odd as it is extremely common in our logs - kind of a bummer as it must contribute a measurable amount to log file size bloat.
Keith Tuomi | Twitter: @itgroove_keith | Blog:
http://yalla.itgroove.net
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

Answer 1

Courtesy of Eric Shupps:
I’ve found what it’s doing but not how to modify the behavior.  In the Microsoft.SharePoint.Diagnostics.ULS class there is a private method called “HandleLoggingGaps”. 
This method is called before trace data is sent to the log in several of the core logging methods.  When called, it checks both the LastSkippedTraceTime value and the last traced time in the current correlation context plus a variable called MaxLoggingGap
against the current date/time.
The MaxLoggingGap value is set by default to 50 milliseconds but there is an environment variable “_ULS_MAX_LOGGING_GAP_IN_MILLISECONDS_” that it will use instead
if that variable contains a value.  This would seem to indicate that the gap time is configurable but I have yet to find the setting that will do so.  I did some reflecting of the powershell cmdlets but so far not found any direct correlation (although
EventLogFloodProtectionQuietPeriod  and EventLogFloodProtectionNotifyInterval in the set-spdiagnosticconfig cmdlet look promising).
Keith Tuomi | Twitter: @itgroove_keith | Blog:
http://yalla.itgroove.net
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.