ULS Logs full of Micro Trace Tags

Question

Hi,
We recently upgraded to SP 2013 and everything went alright.
The server ULS logs are mostly not helpful because its filled with these two messages:
1. Micro Trace Tags: (none)
2. Forced due to logging gap
I have set Diagnostics logging for critical and unexpected events only but the above gets written for medium and verbose. When I look for a corelation id all I get are the above errors. We are on Aug CU, is this a bug?
"The opinions expressed here represent my own and not those of anybody else"

Answer 1

I think its easy to ignore, check the following post for more explanation why Forced Logging gap error
message written:
Link
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).
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog